Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62fdbc19675c32dfcf13b618112232d852716c0a8d28cf8dc3ebd6125459ea25

Tx prefix hash: a80d75668f55002024aa2042d6a4a1ecc013d5e1db106f15ae8ca35c45a5b848
Tx public key: 62872190030e27f703e75e574dd3247d99328f82dd2d64da3abd26b2bf2a85ce
Timestamp: 1764890293 Timestamp [UCT]: 2025-12-04 23:18:13 Age [y:d:h:m:s]: 00:035:04:17:20
Block: 1426600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25180 RingCT/type: yes/0
Extra: 0162872190030e27f703e75e574dd3247d99328f82dd2d64da3abd26b2bf2a85ce021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0078ef814af4f3c9489336e6f9fb3a2e304ed662335891e7a78a019536a2a013 0.600000000000 1915293 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": 1426610, "vin": [ { "gen": { "height": 1426600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0078ef814af4f3c9489336e6f9fb3a2e304ed662335891e7a78a019536a2a013" } } ], "extra": [ 1, 98, 135, 33, 144, 3, 14, 39, 247, 3, 231, 94, 87, 77, 211, 36, 125, 153, 50, 143, 130, 221, 45, 100, 218, 58, 189, 38, 178, 191, 42, 133, 206, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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