Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e24f0084bdb48b2c758a2bd136895a6ec309870e6c157196979ca8f5a0889803

Tx prefix hash: 16421ee57b7edf8cf134181d335d19b54626d5d0e36868b37ff16dd245f1490f
Tx public key: 975e478df50b8b45c04493ab077a390a6e39e2cd637d11fd6755f5aa7c1bd2c7
Timestamp: 1707470942 Timestamp [UCT]: 2024-02-09 09:29:02 Age [y:d:h:m:s]: 00:289:13:26:40
Block: 953677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207322 RingCT/type: yes/0
Extra: 01975e478df50b8b45c04493ab077a390a6e39e2cd637d11fd6755f5aa7c1bd2c70211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d893d080c19ced3446800237f4e4827b0bdbbce8ba9053a39ef15a4d7acdadf 0.600000000000 1412915 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": 953687, "vin": [ { "gen": { "height": 953677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d893d080c19ced3446800237f4e4827b0bdbbce8ba9053a39ef15a4d7acdadf" } } ], "extra": [ 1, 151, 94, 71, 141, 245, 11, 139, 69, 192, 68, 147, 171, 7, 122, 57, 10, 110, 57, 226, 205, 99, 125, 17, 253, 103, 85, 245, 170, 124, 27, 210, 199, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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