Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c5862fcf29356e8569d592a8e14c4e7454a20e5ba3ee148b85c5ddec91f569

Tx prefix hash: 95f2e61aff500c3c086704e662308c9f71f9ed1c3afd1a6321381aa138096d66
Tx public key: 49e9c6f95b54b4d7b57ee7fd2a17cf88c45c0914ef61724c93c122cc659cbfb8
Timestamp: 1735467557 Timestamp [UCT]: 2024-12-29 10:19:17 Age [y:d:h:m:s]: 00:305:12:02:35
Block: 1185651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215859 RingCT/type: yes/0
Extra: 0149e9c6f95b54b4d7b57ee7fd2a17cf88c45c0914ef61724c93c122cc659cbfb8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4d683f893ce5d9214a25d06868ce993185254a7c4c3ed6147bd202fe654ee98 0.600000000000 1672126 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": 1185661, "vin": [ { "gen": { "height": 1185651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4d683f893ce5d9214a25d06868ce993185254a7c4c3ed6147bd202fe654ee98" } } ], "extra": [ 1, 73, 233, 198, 249, 91, 84, 180, 215, 181, 126, 231, 253, 42, 23, 207, 136, 196, 92, 9, 20, 239, 97, 114, 76, 147, 193, 34, 204, 101, 156, 191, 184, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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