Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 505ef832f58b246d868c6e22f4128a51f74f287ef31b7ff569665dc1c917b8ca

Tx prefix hash: c48ea815b62dd3aca6b2c87ae406166ed44ddb5b3c4cf6f222014304b32b6d97
Tx public key: 6b09a6121ec86e5c470f05949478b4ce73da2a1d76ef0362e7d3283b3d71a211
Timestamp: 1749757944 Timestamp [UCT]: 2025-06-12 19:52:24 Age [y:d:h:m:s]: 00:159:03:22:13
Block: 1303668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111457 RingCT/type: yes/0
Extra: 016b09a6121ec86e5c470f05949478b4ce73da2a1d76ef0362e7d3283b3d71a211021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a10686589463ab1d3ead06fa9d4ab937bf3a2836f675280d3d2031f2549d976 0.600000000000 1791251 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": 1303678, "vin": [ { "gen": { "height": 1303668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a10686589463ab1d3ead06fa9d4ab937bf3a2836f675280d3d2031f2549d976" } } ], "extra": [ 1, 107, 9, 166, 18, 30, 200, 110, 92, 71, 15, 5, 148, 148, 120, 180, 206, 115, 218, 42, 29, 118, 239, 3, 98, 231, 211, 40, 59, 61, 113, 162, 17, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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