Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 200d6b62e708fbce09614ff5fb177c6f835e17da200be831c9cdd860ac01e60e

Tx prefix hash: e33c4fb73eb2a40c5c76748968cf27c9d147047b33c3e74fa20c705fe305a88a
Tx public key: 0638c9d92785e03155de1e8e54faaa4fbb989ba1d2dd98012b3f6ecaae65b058
Timestamp: 1707514065 Timestamp [UCT]: 2024-02-09 21:27:45 Age [y:d:h:m:s]: 01:083:15:08:11
Block: 954035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320840 RingCT/type: yes/0
Extra: 010638c9d92785e03155de1e8e54faaa4fbb989ba1d2dd98012b3f6ecaae65b05802110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2071c32a16aa3e9cdce1f5063becd269bad5f95e75b13a3484f29710b0633d88 0.600000000000 1413307 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": 954045, "vin": [ { "gen": { "height": 954035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2071c32a16aa3e9cdce1f5063becd269bad5f95e75b13a3484f29710b0633d88" } } ], "extra": [ 1, 6, 56, 201, 217, 39, 133, 224, 49, 85, 222, 30, 142, 84, 250, 170, 79, 187, 152, 155, 161, 210, 221, 152, 1, 43, 63, 110, 202, 174, 101, 176, 88, 2, 17, 0, 0, 0, 13, 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