Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00c9f9458e13bcdff7f19f179bd66b90e7038e1eeeb34ca8ad2bf37918647f7e

Tx prefix hash: f1177aba2956fd465e41ed850c8e172684cec8710a7b4ee96fe9f2b6fe74fee6
Tx public key: b55c34beec66d0e3350f4f7d0dcc5170d90c9ac1e140a68ff8b43aabf277d8b6
Timestamp: 1725934138 Timestamp [UCT]: 2024-09-10 02:08:58 Age [y:d:h:m:s]: 00:119:09:21:44
Block: 1106756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85372 RingCT/type: yes/0
Extra: 01b55c34beec66d0e3350f4f7d0dcc5170d90c9ac1e140a68ff8b43aabf277d8b6021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0543afc5b76727b39b278cba9eccc1aa6d14df04371a120e0c543e055892982 0.600000000000 1584357 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": 1106766, "vin": [ { "gen": { "height": 1106756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0543afc5b76727b39b278cba9eccc1aa6d14df04371a120e0c543e055892982" } } ], "extra": [ 1, 181, 92, 52, 190, 236, 102, 208, 227, 53, 15, 79, 125, 13, 204, 81, 112, 217, 12, 154, 193, 225, 64, 166, 143, 248, 180, 58, 171, 242, 119, 216, 182, 2, 17, 0, 0, 0, 7, 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