Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4cd3cbeabee221b2757cf99cda54a70d3b11c0306575d6affccc69f8d89806d

Tx prefix hash: f7291a3119d5135d828786ffcb5d14b0e2e0845cd60a48007438b4c97ac74fb6
Tx public key: 7bd1dcc7d22f38256adb39ab69d46affef0582c77d24b773e498f37e008bae6b
Timestamp: 1697442726 Timestamp [UCT]: 2023-10-16 07:52:06 Age [y:d:h:m:s]: 01:196:00:03:27
Block: 870746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401138 RingCT/type: yes/0
Extra: 017bd1dcc7d22f38256adb39ab69d46affef0582c77d24b773e498f37e008bae6b02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.799571056000 dcy

stealth address amount amount idx
00: 05395607c1f471bd65b3426c315c452dc30cf0a388eb5de3c55006e0d8a0fea6 0.799571056000 1325631 of 0

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": 870756, "vin": [ { "gen": { "height": 870746 } } ], "vout": [ { "amount": 799571056, "target": { "key": "05395607c1f471bd65b3426c315c452dc30cf0a388eb5de3c55006e0d8a0fea6" } } ], "extra": [ 1, 123, 209, 220, 199, 210, 47, 56, 37, 106, 219, 57, 171, 105, 212, 106, 255, 239, 5, 130, 199, 125, 36, 183, 115, 228, 152, 243, 126, 0, 139, 174, 107, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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