Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e21cf008cb9066dc1ceb7f98b3c9b3d0bb1b96e125ef18e724316ca72f94265

Tx prefix hash: e43b2d343be5d5bef634d94bee8b47adda0c9f3bd0a7514d755500f9d28bf256
Tx public key: 20fa472729dbfb9be5b158ca6135e91303e3eaefdc6cca9f5280f0ac6c31e625
Timestamp: 1714017392 Timestamp [UCT]: 2024-04-25 03:56:32 Age [y:d:h:m:s]: 00:204:07:44:52
Block: 1007950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146270 RingCT/type: yes/0
Extra: 0120fa472729dbfb9be5b158ca6135e91303e3eaefdc6cca9f5280f0ac6c31e6250211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4c8495968ec3d52ca3abdf81fa2f04ac9a3564e296ffc8c612ade9a850abb84 0.600000000000 1469416 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": 1007960, "vin": [ { "gen": { "height": 1007950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4c8495968ec3d52ca3abdf81fa2f04ac9a3564e296ffc8c612ade9a850abb84" } } ], "extra": [ 1, 32, 250, 71, 39, 41, 219, 251, 155, 229, 177, 88, 202, 97, 53, 233, 19, 3, 227, 234, 239, 220, 108, 202, 159, 82, 128, 240, 172, 108, 49, 230, 37, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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