Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b4fbef2461890362f53d801164da73e71cc810a3905f427169fff6ab5b87afe

Tx prefix hash: d38d0c97c913c2ab652e1836a0a7a8dd49db05ae53650bfa94cf1adde9f525a7
Tx public key: e464ba0d2ff00c036d87e67e94cc0761ddd9cba77a2db5d8dbffcb76e4cac6d3
Timestamp: 1702372415 Timestamp [UCT]: 2023-12-12 09:13:35 Age [y:d:h:m:s]: 01:039:07:03:00
Block: 911423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289402 RingCT/type: yes/0
Extra: 01e464ba0d2ff00c036d87e67e94cc0761ddd9cba77a2db5d8dbffcb76e4cac6d302110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6906511c5513f5e2463bca9e9ac4d1f11dab7e0911fff6bb3f4587ecc75ce99f 0.600000000000 1368625 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": 911433, "vin": [ { "gen": { "height": 911423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6906511c5513f5e2463bca9e9ac4d1f11dab7e0911fff6bb3f4587ecc75ce99f" } } ], "extra": [ 1, 228, 100, 186, 13, 47, 240, 12, 3, 109, 135, 230, 126, 148, 204, 7, 97, 221, 217, 203, 167, 122, 45, 181, 216, 219, 255, 203, 118, 228, 202, 198, 211, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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