Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60adb718ad3454d1b285fd2bca5bcb44494e0113d348175356a0c7f2a93626b5

Tx prefix hash: 2c31f1c09a3027cb715d40f5bb59326300bc9a7605c00002c94a49226af81f61
Tx public key: d28caa810f1596391f17d1fe634f87560ea38b4cef72c0994f925488ea68e7a2
Timestamp: 1736964872 Timestamp [UCT]: 2025-01-15 18:14:32 Age [y:d:h:m:s]: 00:060:18:16:22
Block: 1198049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43220 RingCT/type: yes/0
Extra: 01d28caa810f1596391f17d1fe634f87560ea38b4cef72c0994f925488ea68e7a20211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf881fd6ea86e7164fb6523977fbfdab7eb9659f8f870b6362a54f2de03521c4 0.600000000000 1684666 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": 1198059, "vin": [ { "gen": { "height": 1198049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf881fd6ea86e7164fb6523977fbfdab7eb9659f8f870b6362a54f2de03521c4" } } ], "extra": [ 1, 210, 140, 170, 129, 15, 21, 150, 57, 31, 23, 209, 254, 99, 79, 135, 86, 14, 163, 139, 76, 239, 114, 192, 153, 79, 146, 84, 136, 234, 104, 231, 162, 2, 17, 0, 0, 0, 6, 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