Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a96fe8b1dc4d5f0ed8e472abfdd06912b135934ab53fa4d954f93437b21bb210

Tx prefix hash: 40893743fda9845f8d9a01ad5c0620cc418317638d999c8d007bcfa5730d1471
Tx public key: 517d3dc05da0fe708f28ba4a48e97f3dc878d357de146fbfd6b5fb4fc5e30458
Timestamp: 1717638196 Timestamp [UCT]: 2024-06-06 01:43:16 Age [y:d:h:m:s]: 01:154:03:24:30
Block: 1037972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368739 RingCT/type: yes/0
Extra: 01517d3dc05da0fe708f28ba4a48e97f3dc878d357de146fbfd6b5fb4fc5e3045802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01ae04c525f57ce4b4c4e50436e7881ef4011de0b2f5309aace91111a4403fdc 0.600000000000 1506531 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": 1037982, "vin": [ { "gen": { "height": 1037972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01ae04c525f57ce4b4c4e50436e7881ef4011de0b2f5309aace91111a4403fdc" } } ], "extra": [ 1, 81, 125, 61, 192, 93, 160, 254, 112, 143, 40, 186, 74, 72, 233, 127, 61, 200, 120, 211, 87, 222, 20, 111, 191, 214, 181, 251, 79, 197, 227, 4, 88, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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