Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdf70366c30aedaa7e7ad82843753ca58faa882d7e959df4b0e3d1c97fef5d2c

Tx prefix hash: a008d0c2b325760ae8c8c691446aebe3ffe0cc514e4d3998222ef4ed95ea27f2
Tx public key: 5817c2010aa9e3f3a977a98d4a2e8e551f1c3e342f7cf1fd3798fe1c13e1654a
Timestamp: 1733805336 Timestamp [UCT]: 2024-12-10 04:35:36 Age [y:d:h:m:s]: 00:137:07:03:51
Block: 1171913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97933 RingCT/type: yes/0
Extra: 015817c2010aa9e3f3a977a98d4a2e8e551f1c3e342f7cf1fd3798fe1c13e1654a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 250278b97a5086c096b1184cb97619b7e96caf0706b5a0a500b056557afb7f42 0.600000000000 1657736 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": 1171923, "vin": [ { "gen": { "height": 1171913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250278b97a5086c096b1184cb97619b7e96caf0706b5a0a500b056557afb7f42" } } ], "extra": [ 1, 88, 23, 194, 1, 10, 169, 227, 243, 169, 119, 169, 141, 74, 46, 142, 85, 31, 28, 62, 52, 47, 124, 241, 253, 55, 152, 254, 28, 19, 225, 101, 74, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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