Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99823b4ee00515c851cfc1098b9a57cd06bf86b9f0f07cf080aea827ea581512

Tx prefix hash: 9d1501e97828313c7a9c427f0bb2f965f7cee85f3a2f1e505985bf49d79c59c4
Tx public key: b930f48008e620010bb0adf394cd664e68e09bfc169782b380bb476a87b1d113
Timestamp: 1721091570 Timestamp [UCT]: 2024-07-16 00:59:30 Age [y:d:h:m:s]: 00:333:09:37:35
Block: 1066620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238164 RingCT/type: yes/0
Extra: 01b930f48008e620010bb0adf394cd664e68e09bfc169782b380bb476a87b1d113021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87602de2c55622abfa7fe4b5c8031dae026c713ba4f7f4b9f3e0507f5092aac0 0.600000000000 1537287 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": 1066630, "vin": [ { "gen": { "height": 1066620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87602de2c55622abfa7fe4b5c8031dae026c713ba4f7f4b9f3e0507f5092aac0" } } ], "extra": [ 1, 185, 48, 244, 128, 8, 230, 32, 1, 11, 176, 173, 243, 148, 205, 102, 78, 104, 224, 155, 252, 22, 151, 130, 179, 128, 187, 71, 106, 135, 177, 209, 19, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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