Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd33e36800648112747b43792cd2361c5056b24a306c008c52f0f3486f812522

Tx prefix hash: 756411182e17e4d9a25a62cd31c0c1a478e2995255f2a5b3c48d357b925c4312
Tx public key: 6fad0b1b2a82e30289d45d06ecd6534cce0fe9e4e9febc1c03b16d5b709b4bed
Timestamp: 1733998396 Timestamp [UCT]: 2024-12-12 10:13:16 Age [y:d:h:m:s]: 00:103:01:22:34
Block: 1173525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73417 RingCT/type: yes/0
Extra: 016fad0b1b2a82e30289d45d06ecd6534cce0fe9e4e9febc1c03b16d5b709b4bed021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6835dc9db3e461c04fdf34f46ca66d4a4821fc1ed60dcbc8177422866cce7cca 0.600000000000 1659558 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": 1173535, "vin": [ { "gen": { "height": 1173525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6835dc9db3e461c04fdf34f46ca66d4a4821fc1ed60dcbc8177422866cce7cca" } } ], "extra": [ 1, 111, 173, 11, 27, 42, 130, 227, 2, 137, 212, 93, 6, 236, 214, 83, 76, 206, 15, 233, 228, 233, 254, 188, 28, 3, 177, 109, 91, 112, 155, 75, 237, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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