Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdd34b0ebe3dfaa764f79f31f197d7e88a0784118a324a9424720bf6d3455ffb

Tx prefix hash: df3e0fa855319f774144db08102699987256bb15ebba35d8122d318be98c4ea2
Tx public key: e3707399c6ca42e8e0f9b14cda6fe09c4755bbfd7fdfa73d4a8ca36a697f5057
Timestamp: 1721152869 Timestamp [UCT]: 2024-07-16 18:01:09 Age [y:d:h:m:s]: 00:258:20:11:01
Block: 1067136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184887 RingCT/type: yes/0
Extra: 01e3707399c6ca42e8e0f9b14cda6fe09c4755bbfd7fdfa73d4a8ca36a697f50570211000000015ff1157f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e19da74f99c072744061ea14e4d6aafa0b4cd1f92c40126d1fd111878e694a1 0.600000000000 1537863 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": 1067146, "vin": [ { "gen": { "height": 1067136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e19da74f99c072744061ea14e4d6aafa0b4cd1f92c40126d1fd111878e694a1" } } ], "extra": [ 1, 227, 112, 115, 153, 198, 202, 66, 232, 224, 249, 177, 76, 218, 111, 224, 156, 71, 85, 187, 253, 127, 223, 167, 61, 74, 140, 163, 106, 105, 127, 80, 87, 2, 17, 0, 0, 0, 1, 95, 241, 21, 127, 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