Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47b51f1214ff9968c9c80c497650450e1ea9dd6f9adc9313e1cb7220e704ef13

Tx prefix hash: e4c818d588e39fbb9a68213a8a88e8f7c9fa728725b96b19597683db8dd9053e
Tx public key: 47b4a62e751ca28dbe42501eebf613aa613ffc9556feceb8b84a84f4f91ba884
Timestamp: 1715339828 Timestamp [UCT]: 2024-05-10 11:17:08 Age [y:d:h:m:s]: 01:002:20:56:31
Block: 1018924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262972 RingCT/type: yes/0
Extra: 0147b4a62e751ca28dbe42501eebf613aa613ffc9556feceb8b84a84f4f91ba8840211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c202415d8e5d8244d3623f68b4b59430311bdc1582e1eac50c730dd201740ac6 0.600000000000 1482745 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": 1018934, "vin": [ { "gen": { "height": 1018924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c202415d8e5d8244d3623f68b4b59430311bdc1582e1eac50c730dd201740ac6" } } ], "extra": [ 1, 71, 180, 166, 46, 117, 28, 162, 141, 190, 66, 80, 30, 235, 246, 19, 170, 97, 63, 252, 149, 86, 254, 206, 184, 184, 74, 132, 244, 249, 27, 168, 132, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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