Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b1b17f281e3b8a95c1b0ccbfda818bffff5e29fcecc63e1be720212c1a3a2ed

Tx prefix hash: 1050c355ec3aade5b1b42b502211ada3cb0206cc8198969aa3c872f2b563f030
Tx public key: 84753449b249f590a10da0684845ce963e7f109cae2537e754b1b0cf1faa288b
Timestamp: 1708635731 Timestamp [UCT]: 2024-02-22 21:02:11 Age [y:d:h:m:s]: 01:116:17:50:03
Block: 963336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344389 RingCT/type: yes/0
Extra: 0184753449b249f590a10da0684845ce963e7f109cae2537e754b1b0cf1faa288b02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 064ac65857c6b9d6b1632ab082c9689f140fcf743a45a4f0baf64078c2f6b7fa 0.600000000000 1423037 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": 963346, "vin": [ { "gen": { "height": 963336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "064ac65857c6b9d6b1632ab082c9689f140fcf743a45a4f0baf64078c2f6b7fa" } } ], "extra": [ 1, 132, 117, 52, 73, 178, 73, 245, 144, 161, 13, 160, 104, 72, 69, 206, 150, 62, 127, 16, 156, 174, 37, 55, 231, 84, 177, 176, 207, 31, 170, 40, 139, 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