Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a532e9f11b2ab3283ea4673f32d550668b08d4a3c7a3d40b30a6558f5b9d7281

Tx prefix hash: 09474c8b5721be5eb7c471cca39f4232948aeceb4fcfa30a725c31cf03056c3a
Tx public key: 5789b6843144fb4848feb425e5126011ff73b85e8edb425e7bf26f013a11f42c
Timestamp: 1719136793 Timestamp [UCT]: 2024-06-23 09:59:53 Age [y:d:h:m:s]: 00:311:11:28:22
Block: 1050377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222605 RingCT/type: yes/0
Extra: 015789b6843144fb4848feb425e5126011ff73b85e8edb425e7bf26f013a11f42c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd6d4af5b4521392b97153d04c50cce5b3a4d96be83eac454c03b3787b67fba1 0.600000000000 1520542 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": 1050387, "vin": [ { "gen": { "height": 1050377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd6d4af5b4521392b97153d04c50cce5b3a4d96be83eac454c03b3787b67fba1" } } ], "extra": [ 1, 87, 137, 182, 132, 49, 68, 251, 72, 72, 254, 180, 37, 229, 18, 96, 17, 255, 115, 184, 94, 142, 219, 66, 94, 123, 242, 111, 1, 58, 17, 244, 44, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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