Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 603577f67597f69e63a96f5113398fd4c41c2a65864b5aebb071937a2e7c3ddd

Tx prefix hash: aa360d7e76c4fa9b069dc2bde4e5020e37cc0f321caa9607fffd61b3e5c4c825
Tx public key: f89285340d3b0827e5125150f32905a17fad3697d858c493851967d7df5c582e
Timestamp: 1755212856 Timestamp [UCT]: 2025-08-14 23:07:36 Age [y:d:h:m:s]: 00:167:11:23:31
Block: 1346880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119248 RingCT/type: yes/0
Extra: 01f89285340d3b0827e5125150f32905a17fad3697d858c493851967d7df5c582e021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c68e248c0a42cfd534f5ff1ab1f94e4fba32d12bbb44384430b23b066d75e3f 0.600000000000 1834789 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": 1346890, "vin": [ { "gen": { "height": 1346880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c68e248c0a42cfd534f5ff1ab1f94e4fba32d12bbb44384430b23b066d75e3f" } } ], "extra": [ 1, 248, 146, 133, 52, 13, 59, 8, 39, 229, 18, 81, 80, 243, 41, 5, 161, 127, 173, 54, 151, 216, 88, 196, 147, 133, 25, 103, 215, 223, 92, 88, 46, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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