Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f7010ff849ffd7bc478d36b7c68f038d1c9764f03fa95d1089c4b665eb2fcce

Tx prefix hash: fbacd94fba2aea4d745b2fd9154615b5b0fee7bd2d945501820f3b7e3f55ba43
Tx public key: a82169083768d21e6d5c668d1306518e19bb732fcb6e7d6cb3edd3353928abad
Timestamp: 1713663948 Timestamp [UCT]: 2024-04-21 01:45:48 Age [y:d:h:m:s]: 01:193:11:14:17
Block: 1005018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396924 RingCT/type: yes/0
Extra: 01a82169083768d21e6d5c668d1306518e19bb732fcb6e7d6cb3edd3353928abad02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a37c8f53f9f59debe74f4f3fb6a01d0211fd10b807aa62a58ab9ef86abb482f 0.600000000000 1465596 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": 1005028, "vin": [ { "gen": { "height": 1005018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a37c8f53f9f59debe74f4f3fb6a01d0211fd10b807aa62a58ab9ef86abb482f" } } ], "extra": [ 1, 168, 33, 105, 8, 55, 104, 210, 30, 109, 92, 102, 141, 19, 6, 81, 142, 25, 187, 115, 47, 203, 110, 125, 108, 179, 237, 211, 53, 57, 40, 171, 173, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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