Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afc1247e602b117f47b52e3ec796d12304a7f6cd25440e9cff4ce57ecb04b9ce

Tx prefix hash: c8163c54c1353e03a4dcc89305652b93141c1dec0334ee4a06ce04b60eb5c5c0
Tx public key: b06af3de2fd4ea18881c33c0c7002350692a7c84ca16aa338e05eec9b800d2d3
Timestamp: 1674169750 Timestamp [UCT]: 2023-01-19 23:09:10 Age [y:d:h:m:s]: 02:041:02:57:54
Block: 678462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551020 RingCT/type: yes/0
Extra: 01b06af3de2fd4ea18881c33c0c7002350692a7c84ca16aa338e05eec9b800d2d302110000000152542ceb000000000000000000

1 output(s) for total of 3.467158501000 dcy

stealth address amount amount idx
00: 203ae2e5c0222d4abafabea0d2961ba18dc775c36de47ab615cf136e3c96fdf6 3.467158501000 1120347 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": 678472, "vin": [ { "gen": { "height": 678462 } } ], "vout": [ { "amount": 3467158501, "target": { "key": "203ae2e5c0222d4abafabea0d2961ba18dc775c36de47ab615cf136e3c96fdf6" } } ], "extra": [ 1, 176, 106, 243, 222, 47, 212, 234, 24, 136, 28, 51, 192, 199, 0, 35, 80, 105, 42, 124, 132, 202, 22, 170, 51, 142, 5, 238, 201, 184, 0, 210, 211, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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