Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea3800f3a330667281676a4b310222fa34c873387e0768dd6f1c55ff41e476e

Tx prefix hash: ecc24a0c545cb69482e9092dccca1d391a55f7f8611151f0c3d40a72ad5ae991
Tx public key: 0b5124b3dff6405d541f24ea5a9a055ccc40ec61b8890d455132a9420adbe8b9
Timestamp: 1728571342 Timestamp [UCT]: 2024-10-10 14:42:22 Age [y:d:h:m:s]: 00:155:07:26:00
Block: 1128618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110788 RingCT/type: yes/0
Extra: 010b5124b3dff6405d541f24ea5a9a055ccc40ec61b8890d455132a9420adbe8b9021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8642cb307f298a12248baaeabc4539234a52a455d0aedfd650030cb42d108c6 0.600000000000 1611437 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": 1128628, "vin": [ { "gen": { "height": 1128618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8642cb307f298a12248baaeabc4539234a52a455d0aedfd650030cb42d108c6" } } ], "extra": [ 1, 11, 81, 36, 179, 223, 246, 64, 93, 84, 31, 36, 234, 90, 154, 5, 92, 204, 64, 236, 97, 184, 137, 13, 69, 81, 50, 169, 66, 10, 219, 232, 185, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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