Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b810d1321c872ef4561da3cfc502f7f381f77201f14c090390d1507b9d16f14b

Tx prefix hash: f55e2572e98c3abb73d3f91c2e0a9fc2c7aa3296a737e73a1c4a3a14e3fa27da
Tx public key: e069a5d03391fed875729bbe51b4dfc8f8d81316a4290cb15d6a153610cd9ee7
Timestamp: 1741633066 Timestamp [UCT]: 2025-03-10 18:57:46 Age [y:d:h:m:s]: 00:328:19:15:07
Block: 1236440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232666 RingCT/type: yes/0
Extra: 01e069a5d03391fed875729bbe51b4dfc8f8d81316a4290cb15d6a153610cd9ee70211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba9ac41bba76eafd038d2b792076bded94685cc1258d17746dd22f51ba334b3c 0.600000000000 1723387 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": 1236450, "vin": [ { "gen": { "height": 1236440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba9ac41bba76eafd038d2b792076bded94685cc1258d17746dd22f51ba334b3c" } } ], "extra": [ 1, 224, 105, 165, 208, 51, 145, 254, 216, 117, 114, 155, 190, 81, 180, 223, 200, 248, 216, 19, 22, 164, 41, 12, 177, 93, 106, 21, 54, 16, 205, 158, 231, 2, 17, 0, 0, 0, 1, 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