Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4bc3d3f7f87762abeb1a7b90aca06d040dbc164275ea0596366083ddd46bff3a

Tx prefix hash: 30ae71ba3bc971435570e5706bb1aa360ae4829135b10947a92b29d7463a1851
Tx public key: a0b072c6d39f383c1039f8c52b0db7da473c47c86f97c5a00150b84b1b096cc5
Timestamp: 1725591735 Timestamp [UCT]: 2024-09-06 03:02:15 Age [y:d:h:m:s]: 00:208:13:24:56
Block: 1103912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148898 RingCT/type: yes/0
Extra: 01a0b072c6d39f383c1039f8c52b0db7da473c47c86f97c5a00150b84b1b096cc502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05faf850429b1078e00190f511c37ea99b055898c7bba597b03b0902cbb5a66c 0.600000000000 1580927 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1103922, "vin": [ { "gen": { "height": 1103912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05faf850429b1078e00190f511c37ea99b055898c7bba597b03b0902cbb5a66c" } } ], "extra": [ 1, 160, 176, 114, 198, 211, 159, 56, 60, 16, 57, 248, 197, 43, 13, 183, 218, 71, 60, 71, 200, 111, 151, 197, 160, 1, 80, 184, 75, 27, 9, 108, 197, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8