Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 565a8a0800a6eede0a9e6de06ba5a9d9a8117740d3b115e830a9b1eb5c3dda04

Tx prefix hash: 94eb01d1b478a1e085bc81017738635d2c50950ecda75591084f85e4ab2110c3
Tx public key: 192d3055796df349c95bffa081d8adf03a817f823747bec897bc2ef30182710e
Timestamp: 1713679430 Timestamp [UCT]: 2024-04-21 06:03:50 Age [y:d:h:m:s]: 01:193:09:14:33
Block: 1005149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396861 RingCT/type: yes/0
Extra: 01192d3055796df349c95bffa081d8adf03a817f823747bec897bc2ef30182710e0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9e0c07fb231407da93a7de986cf03d7e645eaec879ae1d6cd9927e4eadb336a 0.600000000000 1465729 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": 1005159, "vin": [ { "gen": { "height": 1005149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9e0c07fb231407da93a7de986cf03d7e645eaec879ae1d6cd9927e4eadb336a" } } ], "extra": [ 1, 25, 45, 48, 85, 121, 109, 243, 73, 201, 91, 255, 160, 129, 216, 173, 240, 58, 129, 127, 130, 55, 71, 190, 200, 151, 188, 46, 243, 1, 130, 113, 14, 2, 17, 0, 0, 0, 5, 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