Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222ea56688e7cf33c645d1680b1f54ddd71cdae9c3be7b0208e38546ceccf513

Tx prefix hash: ad824301595b808a6c575d3217a836b307cbc167ec29ad8cc4c51df7c9cb537f
Tx public key: 51e0e1587cf1a3d565ab8fb31a97827273d777eff67f5a1b92ad15890b9e12c7
Timestamp: 1703199915 Timestamp [UCT]: 2023-12-21 23:05:15 Age [y:d:h:m:s]: 01:348:06:17:28
Block: 918272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507779 RingCT/type: yes/0
Extra: 0151e0e1587cf1a3d565ab8fb31a97827273d777eff67f5a1b92ad15890b9e12c70211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b3922fcf3b8a6728078426ee2b263ffdfa9788d01e143e5117d93d4c0a5e424 0.600000000000 1375914 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": 918282, "vin": [ { "gen": { "height": 918272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b3922fcf3b8a6728078426ee2b263ffdfa9788d01e143e5117d93d4c0a5e424" } } ], "extra": [ 1, 81, 224, 225, 88, 124, 241, 163, 213, 101, 171, 143, 179, 26, 151, 130, 114, 115, 215, 119, 239, 246, 127, 90, 27, 146, 173, 21, 137, 11, 158, 18, 199, 2, 17, 0, 0, 0, 8, 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