Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95ad6b5a58eb8eed0a28e944ee5b6099e81eabab8f41287058398572974f96e2

Tx prefix hash: 9b2731acfd835ecc803b2416090f6ec79d6e4713f253946c66db025a68306d1e
Tx public key: c0a1b2aca536bf2e06cca6bfc3f4121a529e70aa084a82d18bf9bab7548ef5d2
Timestamp: 1695636871 Timestamp [UCT]: 2023-09-25 10:14:31 Age [y:d:h:m:s]: 01:060:17:39:50
Block: 855765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304666 RingCT/type: yes/0
Extra: 01c0a1b2aca536bf2e06cca6bfc3f4121a529e70aa084a82d18bf9bab7548ef5d202110000000533af99f4000000000000000000

1 output(s) for total of 0.896386605000 dcy

stealth address amount amount idx
00: 8054e784434e2320fef227c3420b17f1caa3ef7afebf002691b58e2becc78deb 0.896386605000 1309803 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": 855775, "vin": [ { "gen": { "height": 855765 } } ], "vout": [ { "amount": 896386605, "target": { "key": "8054e784434e2320fef227c3420b17f1caa3ef7afebf002691b58e2becc78deb" } } ], "extra": [ 1, 192, 161, 178, 172, 165, 54, 191, 46, 6, 204, 166, 191, 195, 244, 18, 26, 82, 158, 112, 170, 8, 74, 130, 209, 139, 249, 186, 183, 84, 142, 245, 210, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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