Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57b6c39cdbcdb15b004511bb76c5907b84b0d92f9e87c40051c55d3e8db7af23

Tx prefix hash: 97364c09747a4b9bdcd0ebe9d86c97167faea135ee0be4afb574388c1ee1c4f9
Tx public key: 467950ec965d4bb32df01e39126b5c6a6ec73a12562d952dad12ae11cda4cae7
Timestamp: 1730960025 Timestamp [UCT]: 2024-11-07 06:13:45 Age [y:d:h:m:s]: 00:076:13:44:32
Block: 1148334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54745 RingCT/type: yes/0
Extra: 01467950ec965d4bb32df01e39126b5c6a6ec73a12562d952dad12ae11cda4cae70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b69a79379b027dbab2216b788cb5d3cde6ea5d376b9144e4ae39cf5bfa86f6 0.600000000000 1633151 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": 1148344, "vin": [ { "gen": { "height": 1148334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b69a79379b027dbab2216b788cb5d3cde6ea5d376b9144e4ae39cf5bfa86f6" } } ], "extra": [ 1, 70, 121, 80, 236, 150, 93, 75, 179, 45, 240, 30, 57, 18, 107, 92, 106, 110, 199, 58, 18, 86, 45, 149, 45, 173, 18, 174, 17, 205, 164, 202, 231, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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