Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b36649d12117b7a107d908abd406079402f7f264dc032c8f4afe8d3114ba4a81

Tx prefix hash: d21e47768b5e1d9360914b101245dda8d7b8057600769f9a19c73259e514dae1
Tx public key: 82dcdc3ec5e42baa59109afb16607e6d9e7067d9996e7a430631593c84d06253
Timestamp: 1712943858 Timestamp [UCT]: 2024-04-12 17:44:18 Age [y:d:h:m:s]: 01:202:07:08:15
Block: 999034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403264 RingCT/type: yes/0
Extra: 0182dcdc3ec5e42baa59109afb16607e6d9e7067d9996e7a430631593c84d062530211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1cff823e33c413b8876e25d748bd0004816a94a3e202957a413520840c47924 0.600000000000 1459510 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": 999044, "vin": [ { "gen": { "height": 999034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1cff823e33c413b8876e25d748bd0004816a94a3e202957a413520840c47924" } } ], "extra": [ 1, 130, 220, 220, 62, 197, 228, 43, 170, 89, 16, 154, 251, 22, 96, 126, 109, 158, 112, 103, 217, 153, 110, 122, 67, 6, 49, 89, 60, 132, 208, 98, 83, 2, 17, 0, 0, 0, 2, 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