Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3226b60bdaaa7284b580dc6242d04e724ed9af987fac07cfca1ca992451acd7

Tx prefix hash: 5ea41c5897c30bd9b7359c45552f8e2e8fce58ab91923b908c03cc8d1e598f48
Tx public key: 01d5c850b08c996a63e5aafe677c5377ac86e84b894d1fc799098d511e1f3782
Timestamp: 1733024240 Timestamp [UCT]: 2024-12-01 03:37:20 Age [y:d:h:m:s]: 01:037:03:10:22
Block: 1165433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285003 RingCT/type: yes/0
Extra: 0101d5c850b08c996a63e5aafe677c5377ac86e84b894d1fc799098d511e1f37820211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ecd5479ae74fccc8aa17b91567b460bc7b08598ae31e288c8b4798ad16eb5e2 0.600000000000 1651108 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": 1165443, "vin": [ { "gen": { "height": 1165433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ecd5479ae74fccc8aa17b91567b460bc7b08598ae31e288c8b4798ad16eb5e2" } } ], "extra": [ 1, 1, 213, 200, 80, 176, 140, 153, 106, 99, 229, 170, 254, 103, 124, 83, 119, 172, 134, 232, 75, 137, 77, 31, 199, 153, 9, 141, 81, 30, 31, 55, 130, 2, 17, 0, 0, 0, 3, 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