Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8adf65eaf1571c1ef73d49a6f5658e267868284f830f67ae24ee3dc2ab6caa03

Tx prefix hash: 848f71e70fb504f739b793644f59929e52e7fd077a9c69be85bdfaa5c5cbbe8b
Tx public key: 9fa9c9a303302cbb866d9bb6be6e26e7aa1315bc339cba378f1125a38b8630ca
Timestamp: 1762824654 Timestamp [UCT]: 2025-11-11 01:30:54 Age [y:d:h:m:s]: 00:009:20:57:05
Block: 1409462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7068 RingCT/type: yes/0
Extra: 019fa9c9a303302cbb866d9bb6be6e26e7aa1315bc339cba378f1125a38b8630ca02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0afdbde497bb27a05d3e13c19d1d5b9eff274dfbcbb059498e7fd8275366c7e9 0.600000000000 1897907 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": 1409472, "vin": [ { "gen": { "height": 1409462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0afdbde497bb27a05d3e13c19d1d5b9eff274dfbcbb059498e7fd8275366c7e9" } } ], "extra": [ 1, 159, 169, 201, 163, 3, 48, 44, 187, 134, 109, 155, 182, 190, 110, 38, 231, 170, 19, 21, 188, 51, 156, 186, 55, 143, 17, 37, 163, 139, 134, 48, 202, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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