Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3df5d7ec0e4f9b4ba8d53948478bd0a3cbee5e6233957350638de0e59397807e

Tx prefix hash: 06e5588fca7810ac4bc8c400a3cda73239590d0ae5e602c643dc1bed649176a3
Tx public key: df2a9a8a043a556a753cafd80690a429b50b38758df8ced4b869bd617e0dd379
Timestamp: 1706622056 Timestamp [UCT]: 2024-01-30 13:40:56 Age [y:d:h:m:s]: 01:029:23:57:05
Block: 946626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282484 RingCT/type: yes/0
Extra: 01df2a9a8a043a556a753cafd80690a429b50b38758df8ced4b869bd617e0dd3790211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8128cc19ba8b0f554b347d3cd8fbc65aa196df104b184b332260e0256056db6 0.600000000000 1404960 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": 946636, "vin": [ { "gen": { "height": 946626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8128cc19ba8b0f554b347d3cd8fbc65aa196df104b184b332260e0256056db6" } } ], "extra": [ 1, 223, 42, 154, 138, 4, 58, 85, 106, 117, 60, 175, 216, 6, 144, 164, 41, 181, 11, 56, 117, 141, 248, 206, 212, 184, 105, 189, 97, 126, 13, 211, 121, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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