Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad6caf01400b1701d31d9e557e714fa0f5393771c3d8b6948108ca992e0a27c7

Tx prefix hash: 4b8cc0d302981943297c23158ce3033294d6a8f02fd371024e922ddcb50f191b
Tx public key: 5186772a44766096a9de962cf60f7d6762d892b8014b62fe1bf76d83fd42e94f
Timestamp: 1733178626 Timestamp [UCT]: 2024-12-02 22:30:26 Age [y:d:h:m:s]: 00:050:06:28:50
Block: 1166715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35908 RingCT/type: yes/0
Extra: 015186772a44766096a9de962cf60f7d6762d892b8014b62fe1bf76d83fd42e94f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c19be794746dcb9ff8cfb1cbd6e2b6a928df2b4e31f33e52861048fc77a47125 0.600000000000 1652404 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": 1166725, "vin": [ { "gen": { "height": 1166715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c19be794746dcb9ff8cfb1cbd6e2b6a928df2b4e31f33e52861048fc77a47125" } } ], "extra": [ 1, 81, 134, 119, 42, 68, 118, 96, 150, 169, 222, 150, 44, 246, 15, 125, 103, 98, 216, 146, 184, 1, 75, 98, 254, 27, 247, 109, 131, 253, 66, 233, 79, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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