Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c04d16f295f84079299726ba286b42fa47d1ec890e5dd1a30323c6c64f19d7c

Tx prefix hash: 889040f1e83b152174b3476e318a63d680ff4b3ead10ae13d7a075e8fb73c640
Tx public key: d88505d629bb533bb8aecf93cdeea3caa305b9ceab79c39269e5370c6f9c6bb2
Timestamp: 1716747263 Timestamp [UCT]: 2024-05-26 18:14:23 Age [y:d:h:m:s]: 00:232:00:15:20
Block: 1030599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166037 RingCT/type: yes/0
Extra: 01d88505d629bb533bb8aecf93cdeea3caa305b9ceab79c39269e5370c6f9c6bb20211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3febdaa1808e2d3eef912ae83b9fd3557a9f1357ba79135fc285c9323eb6dda8 0.600000000000 1498856 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": 1030609, "vin": [ { "gen": { "height": 1030599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3febdaa1808e2d3eef912ae83b9fd3557a9f1357ba79135fc285c9323eb6dda8" } } ], "extra": [ 1, 216, 133, 5, 214, 41, 187, 83, 59, 184, 174, 207, 147, 205, 238, 163, 202, 163, 5, 185, 206, 171, 121, 195, 146, 105, 229, 55, 12, 111, 156, 107, 178, 2, 17, 0, 0, 0, 3, 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