Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b10487945a587b33a49c9de2c86ca213653b2f71ddabb4ce39fc1be8bcfc86d

Tx prefix hash: 1e98faccc7c62ed1ab66aada7decc19245fc1ccd88b7f8f360c03ffbd5047640
Tx public key: e9e407a00bd0efc019d9fcbc5de8dc5bd1bae71e925caa740e8db0b9ccc31697
Timestamp: 1758328338 Timestamp [UCT]: 2025-09-20 00:32:18 Age [y:d:h:m:s]: 00:111:22:33:30
Block: 1372197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80180 RingCT/type: yes/0
Extra: 01e9e407a00bd0efc019d9fcbc5de8dc5bd1bae71e925caa740e8db0b9ccc31697021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 865700a84a5ccf58ae7c645a8ef0d179bf3d1334a1057466493924d1404d0f30 0.600000000000 1860282 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": 1372207, "vin": [ { "gen": { "height": 1372197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "865700a84a5ccf58ae7c645a8ef0d179bf3d1334a1057466493924d1404d0f30" } } ], "extra": [ 1, 233, 228, 7, 160, 11, 208, 239, 192, 25, 217, 252, 188, 93, 232, 220, 91, 209, 186, 231, 30, 146, 92, 170, 116, 14, 141, 176, 185, 204, 195, 22, 151, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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