Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89a7a8b3f3f5d9ffd57a701c50683c45188ce80a0253b16089e582f7b64255ec

Tx prefix hash: 096e0663b3813c85c001549bbbd3a9f291d28af84d0cacb25948b12a36092502
Tx public key: fc86bd3c78eea753bbe5e031140ac5b41afbd6c9a04fe524f80c26ab1fe18940
Timestamp: 1708634426 Timestamp [UCT]: 2024-02-22 20:40:26 Age [y:d:h:m:s]: 01:043:23:55:14
Block: 963323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292462 RingCT/type: yes/0
Extra: 01fc86bd3c78eea753bbe5e031140ac5b41afbd6c9a04fe524f80c26ab1fe1894002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a17ffc2f8d8065c532bb899bd0b5e036f6d539d245e33d0d3f12f92149f6ada 0.600000000000 1423024 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": 963333, "vin": [ { "gen": { "height": 963323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a17ffc2f8d8065c532bb899bd0b5e036f6d539d245e33d0d3f12f92149f6ada" } } ], "extra": [ 1, 252, 134, 189, 60, 120, 238, 167, 83, 187, 229, 224, 49, 20, 10, 197, 180, 26, 251, 214, 201, 160, 79, 229, 36, 248, 12, 38, 171, 31, 225, 137, 64, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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