Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19cd70d718951e51ca6959a4f49ced21985b44de4b21a23fe0699a9a065e7398

Tx prefix hash: 897283b2b155cb7aad41e017be6cd3962a69862b7b85581e9f97a910f3e34e1f
Tx public key: f9fa9c8a19137fb26083a2051268c02d3ab51ee7da99d495813c6f40b325df51
Timestamp: 1696708768 Timestamp [UCT]: 2023-10-07 19:59:28 Age [y:d:h:m:s]: 01:223:20:07:09
Block: 864658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421049 RingCT/type: yes/0
Extra: 01f9fa9c8a19137fb26083a2051268c02d3ab51ee7da99d495813c6f40b325df51021100000005faf35c9c000000000000000000

1 output(s) for total of 0.837585489000 dcy

stealth address amount amount idx
00: 5519a29d9d17c857fae842758fa663832aa544cdf696000676aa13ad0d5134e0 0.837585489000 1319178 of 0

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": 864668, "vin": [ { "gen": { "height": 864658 } } ], "vout": [ { "amount": 837585489, "target": { "key": "5519a29d9d17c857fae842758fa663832aa544cdf696000676aa13ad0d5134e0" } } ], "extra": [ 1, 249, 250, 156, 138, 25, 19, 127, 178, 96, 131, 162, 5, 18, 104, 192, 45, 58, 181, 30, 231, 218, 153, 212, 149, 129, 60, 111, 64, 179, 37, 223, 81, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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