Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb522e49b4d849addf3d40ff07318a904334e00f63703a023c60d0978da6bb17

Tx prefix hash: ef23ed6d96caae6ddcf906ee6c8b1f4e5a9d7c956701647f5184978a6bf037ad
Tx public key: e8124ab59f9e8b88c624bd2bb7bf048546160a86e37ee20b4a51665455995e97
Timestamp: 1734289479 Timestamp [UCT]: 2024-12-15 19:04:39 Age [y:d:h:m:s]: 00:093:01:36:04
Block: 1175930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66294 RingCT/type: yes/0
Extra: 01e8124ab59f9e8b88c624bd2bb7bf048546160a86e37ee20b4a51665455995e970211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 523e2d94b37a3a0bf1f377b4eebf878dc2b753fa04bc3b107e6bdec300d7ebd0 0.600000000000 1662257 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": 1175940, "vin": [ { "gen": { "height": 1175930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "523e2d94b37a3a0bf1f377b4eebf878dc2b753fa04bc3b107e6bdec300d7ebd0" } } ], "extra": [ 1, 232, 18, 74, 181, 159, 158, 139, 136, 198, 36, 189, 43, 183, 191, 4, 133, 70, 22, 10, 134, 227, 126, 226, 11, 74, 81, 102, 84, 85, 153, 94, 151, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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