Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 601d27024520a8f1c7be6f21393b2ffe49ddaad180f6de9e85cf99945b1c90f3

Tx prefix hash: d8bfc977baed6198e0f634710f455cfb7dd1f5c0d2eb10bebfe81beb9c378605
Tx public key: 42b6f78b74c079d39761ef1b14f6ffa50a9b0ddcc2b148df4cb933183a3ba4d8
Timestamp: 1713730097 Timestamp [UCT]: 2024-04-21 20:08:17 Age [y:d:h:m:s]: 00:249:13:13:54
Block: 1005566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178628 RingCT/type: yes/0
Extra: 0142b6f78b74c079d39761ef1b14f6ffa50a9b0ddcc2b148df4cb933183a3ba4d80211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b95d5a7afd3de30ce58773b0b131159391927ea9592eb26986d452438d53994 0.600000000000 1466300 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": 1005576, "vin": [ { "gen": { "height": 1005566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b95d5a7afd3de30ce58773b0b131159391927ea9592eb26986d452438d53994" } } ], "extra": [ 1, 66, 182, 247, 139, 116, 192, 121, 211, 151, 97, 239, 27, 20, 246, 255, 165, 10, 155, 13, 220, 194, 177, 72, 223, 76, 185, 51, 24, 58, 59, 164, 216, 2, 17, 0, 0, 0, 7, 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