Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b113f37ac28395b775386436b406eff6a6f19e2780a65c6cfcc13cd5e59196e

Tx prefix hash: f09df1652e9da0a81867e205a652accff676073f8cdf6afac6b6bc0d9503e397
Tx public key: 16e7611fc268bf6c41e1e96e55d3b9a467b69204aa5dab5d9c1860fa7b3a7478
Timestamp: 1760812767 Timestamp [UCT]: 2025-10-18 18:39:27 Age [y:d:h:m:s]: 00:026:05:18:48
Block: 1392805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18772 RingCT/type: yes/0
Extra: 0116e7611fc268bf6c41e1e96e55d3b9a467b69204aa5dab5d9c1860fa7b3a74780211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 536baac7d63b61ccdbd327db226eb008dfafb42703b983f2514fdbdb9cb2ccac 0.600000000000 1881060 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": 1392815, "vin": [ { "gen": { "height": 1392805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "536baac7d63b61ccdbd327db226eb008dfafb42703b983f2514fdbdb9cb2ccac" } } ], "extra": [ 1, 22, 231, 97, 31, 194, 104, 191, 108, 65, 225, 233, 110, 85, 211, 185, 164, 103, 182, 146, 4, 170, 93, 171, 93, 156, 24, 96, 250, 123, 58, 116, 120, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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