Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34b5a0d394bf8229483aedfee75193173e33235cca1b575d49187c5c638884d

Tx prefix hash: ded81afe391da1a0bb5763d9951b8fcbeb5243f4f9ba4bc51cffca9c6ed8c9c5
Tx public key: a704db940149e85b6a8aad6cc63cc415fc01761b14ec4d8977cb76c5b06c6850
Timestamp: 1708347899 Timestamp [UCT]: 2024-02-19 13:04:59 Age [y:d:h:m:s]: 01:091:05:03:16
Block: 960955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326243 RingCT/type: yes/0
Extra: 01a704db940149e85b6a8aad6cc63cc415fc01761b14ec4d8977cb76c5b06c685002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aadf1666c766d09aa8c6418a6669a84b9108992ee803d08f2f739ee021b0f2d5 0.600000000000 1420542 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": 960965, "vin": [ { "gen": { "height": 960955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aadf1666c766d09aa8c6418a6669a84b9108992ee803d08f2f739ee021b0f2d5" } } ], "extra": [ 1, 167, 4, 219, 148, 1, 73, 232, 91, 106, 138, 173, 108, 198, 60, 196, 21, 252, 1, 118, 27, 20, 236, 77, 137, 119, 203, 118, 197, 176, 108, 104, 80, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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