Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a76d5e7e574a7404e60eb48dfc52cff536574dddb3d8e47dd5a7bab048e55e00

Tx prefix hash: 6042b42b0ba4edc83ad8064ac73afc221f30f62160cd22f8d78005b3956bff2f
Tx public key: 86b20f38b5fbef26974a00ced4861ed1c32bfcd2a0dee8aabe38dcf4f78f94e4
Timestamp: 1713554170 Timestamp [UCT]: 2024-04-19 19:16:10 Age [y:d:h:m:s]: 00:275:13:36:22
Block: 1004096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197212 RingCT/type: yes/0
Extra: 0186b20f38b5fbef26974a00ced4861ed1c32bfcd2a0dee8aabe38dcf4f78f94e402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8ba8d716eacdeb066bce37ea471d6aee12525e917ae8ac4e60205daf5efc8d4 0.600000000000 1464662 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": 1004106, "vin": [ { "gen": { "height": 1004096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8ba8d716eacdeb066bce37ea471d6aee12525e917ae8ac4e60205daf5efc8d4" } } ], "extra": [ 1, 134, 178, 15, 56, 181, 251, 239, 38, 151, 74, 0, 206, 212, 134, 30, 209, 195, 43, 252, 210, 160, 222, 232, 170, 190, 56, 220, 244, 247, 143, 148, 228, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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