Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee16043996a3f1ccdbd4d86d383459d288bcaa37e0b455211de030a31e6f77ad

Tx prefix hash: 75252f9bea0554ee3734ed97b8b996d37ba366e4e9e9b8a2beada73730db26d9
Tx public key: a216fbaa2fa2925f65c3587b6f6a306566d7480281d3ecc4ce2cf3b5a01f9bee
Timestamp: 1581361465 Timestamp [UCT]: 2020-02-10 19:04:25 Age [y:d:h:m:s]: 05:000:03:49:29
Block: 62197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152905 RingCT/type: yes/0
Extra: 01a216fbaa2fa2925f65c3587b6f6a306566d7480281d3ecc4ce2cf3b5a01f9bee0211000001cd7adf42d3000000000000000000

1 output(s) for total of 381.870697894000 dcy

stealth address amount amount idx
00: a219ecfb3493adab5c0dd2aebdbd3bbe463a847aeae7d8485e73ba38935c757d 381.870697894000 114710 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": 62207, "vin": [ { "gen": { "height": 62197 } } ], "vout": [ { "amount": 381870697894, "target": { "key": "a219ecfb3493adab5c0dd2aebdbd3bbe463a847aeae7d8485e73ba38935c757d" } } ], "extra": [ 1, 162, 22, 251, 170, 47, 162, 146, 95, 101, 195, 88, 123, 111, 106, 48, 101, 102, 215, 72, 2, 129, 211, 236, 196, 206, 44, 243, 181, 160, 31, 155, 238, 2, 17, 0, 0, 1, 205, 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