Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c110087b7c512847d9e5c0d4da9b7aa30a93d7d85319f9f4d8443d4b0dee6c70

Tx prefix hash: a73c0f08963a3cc9ecf38a2be0af2910f83eb3cdf1ce38601b15efece55ce3ef
Tx public key: 6ba735a1b67a4070b38877fb69c600a4ecf3a8aaf3ea41c206ad34ab85e7f03f
Timestamp: 1582291942 Timestamp [UCT]: 2020-02-21 13:32:22 Age [y:d:h:m:s]: 04:312:00:58:50
Block: 69492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115567 RingCT/type: yes/0
Extra: 016ba735a1b67a4070b38877fb69c600a4ecf3a8aaf3ea41c206ad34ab85e7f03f0211000000017adf42d3000000000000000000

1 output(s) for total of 361.197687301000 dcy

stealth address amount amount idx
00: ee57085c34e3b567a6458cc4bbc41b27d106daf561237a2241329142abc8d59a 361.197687301000 128191 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": 69502, "vin": [ { "gen": { "height": 69492 } } ], "vout": [ { "amount": 361197687301, "target": { "key": "ee57085c34e3b567a6458cc4bbc41b27d106daf561237a2241329142abc8d59a" } } ], "extra": [ 1, 107, 167, 53, 161, 182, 122, 64, 112, 179, 136, 119, 251, 105, 198, 0, 164, 236, 243, 168, 170, 243, 234, 65, 194, 6, 173, 52, 171, 133, 231, 240, 63, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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