5fbeea3aef199e56f31a6c4e4bcd5d8b52d7846aca478035d253abc0e3fe7d7c
Summary
Location |
73,868 confirmations
|
---|
Inputs |
6
6,034,745 sats
|
---|---|
Outputs |
6
6,000,000 sats
|
Fee | 34,745 sats |
---|---|
Size | 604.00 vbytes |
Feerate | 57.52 sats/vbyte |
Features | Segwit RBF |
---|
Transaction Data
1
- Basic Transaction
Inputs (6)
Raw Transaction
Bytes | 1,090 | 442 + 648 |
---|---|---|
Weight Units | 2,416 | 442 x 4 + 648 x 1 |
Virtual Bytes | 604.00 | 442 x 1 + 648 x 0.25 |
01000000000106acd36d8f94735d9020cfad9ca3a089aee360f2713c1cf9091e8ad197503522040000000000ffffffff329ec19b055961564e4caf0eab388efa830c15e4b6710a78c928fd2ef65573650400000000ffffffff5ecaea9f57f144274b81d5dbda40bd4eb630cb9e3ad02eaf0739fa76b623b3750400000000ffffffff23226d066cbc1bf67606abe22170ef4347b18c028dddafb22e3bf53f770ea78f0200000000ffffffff8c1082a989f15f334c5fe9457259abf06b061bcb4d66113ccaf3fcb2af9cb4a30400000000ffffffffcc5db8e8a4bd5ae1d67a80836ac0d43aba4a15d4cc748060d222731dfd848df70600000000ffffffff0640420f0000000000160014312ada0bc3a40557c969732b04119193be402c8140420f0000000000160014322c86285b75f6c38285576967e9cd451f0c4c4640420f000000000016001469da840e8a65852c9c6fcee7aadddcdd2e61292d40420f00000000001600146e72d91c11e595a349fa0d8ac89ffd5feac449b840420f000000000016001484e174cb9916e94ed93049004983470dd52fb03d40420f0000000000160014985594c2095d414a8bc1cee62d237273ae5ef0c80248304502210093adb0a58b64b58dfdbcfc0e0099eda5d3cfe79187cd7f96194ba56ba493a7bc022014dd9d9ac12f32a396fa17e96d237ebb50ed9dc0bd771a2ae434cdecfa9acb9a012102292107f763ff7e36a5bfcc96de6fb2855c1a03331a0322ef1afe343c0595b17f02483045022100c0726091b0f94d4e01b61254c7a782a0194ee5eb0085701edf65a448a4abdbbb02202a1f3401e6141863926d88f2fb31a2c41a9f74ccb92e24871cdc6149cd29c02b0121034341150d25b40307f9ae23c5e312c7d083d6970572a7369be639a6b18813491702473044022100ce31ad657ee5aa98e52f6018f22f53df1067fbdd1d6cf20488a5af07a0fdcf38021f0943ff16bb1d1e330f9218ed51a06ad56b1f48bfc78f60dcf3bb0b0976e9020121022e9d34031b4afcdfd7a5f822e8a21e514b33b3d808ea78be3d1a675dabb35f4d02483045022100d8b0a41adff48bdadc4bc3f1e1ea2c2523a0b6242b260aaac9dbce7cd198a389022040c2e1e8f34dfea7dc3651f1910d70d932c9c8195037c2323f0c5712290a9094012103d2cd154b40f17219824d571cfd5ae1046e669f1531fe8c93afb37f2c90f52d8802483045022100945d74dd10195be27afe7ed2323d3379f6b2c986a42a0d24f3cb0bdb1ed9391f02201442bfe4572452c7656c957923fbb7ecaa8c5b65b20ca116589c1e063ed36eab012103aa8fae4e42f5a52278763416f70cc5f490ca58ec74940c77c233fc847e8497440247304402204da950836bc516872a9d60d766799783080f7b821a1f5c59b49bde6973860a6b0220043e966878de46a0fb4cbd704f1d1f6432bda5f837e5ed00ce1ce976ab4ca8f8012103a2cf0ea7c649634768fa4ab2361708eb4b3400844e027c1aca10a22595dd42b600000000
wTXID
bf43149cf1294c0e3c6b819634f11b6c1e2d0d555855b54e4f437df36e8212fa
The wTXID is the hash of the entire transaction data (including witness data).