Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1cbab432aee66ff1151bdd4d734d91e5c1c5ecfe446e33e3beb27c10965398f

Tx prefix hash: c49de1f9523e347e6ff5ae61b5f0f99e0a6628e1a1b79fff616fd880c80e285f
Tx public key: 7e316c8a8f29219e9c9a5e2c40f61357385dbead648e6599182f56d7c14cf78c
Timestamp: 1706351177 Timestamp [UCT]: 2024-01-27 10:26:17 Age [y:d:h:m:s]: 01:286:10:44:40
Block: 944379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463526 RingCT/type: yes/0
Extra: 017e316c8a8f29219e9c9a5e2c40f61357385dbead648e6599182f56d7c14cf78c02110000000510a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75ec5e2743eef7e48d3cf97e49ff78d6fd9af4267d3d5df839b8e1e8f1bee826 0.600000000000 1402615 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": 944389, "vin": [ { "gen": { "height": 944379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75ec5e2743eef7e48d3cf97e49ff78d6fd9af4267d3d5df839b8e1e8f1bee826" } } ], "extra": [ 1, 126, 49, 108, 138, 143, 41, 33, 158, 156, 154, 94, 44, 64, 246, 19, 87, 56, 93, 190, 173, 100, 142, 101, 153, 24, 47, 86, 215, 193, 76, 247, 140, 2, 17, 0, 0, 0, 5, 16, 161, 116, 143, 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