Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00e27d8e1804da65dd29a98fbe4d17cc46f4c6b4f5edd098cd3adeeb9e99b353

Tx prefix hash: 37d96c4f765e27c3b0976f04c20e1bd78f069bda3cf3195ed207cc0bd24686bc
Tx public key: 83668599b69e0fe0d06dae02470511c1d216959af10bdbc68e9fbf8b1b7751c7
Timestamp: 1580980363 Timestamp [UCT]: 2020-02-06 09:12:43 Age [y:d:h:m:s]: 04:286:09:55:28
Block: 59922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095955 RingCT/type: yes/0
Extra: 0183668599b69e0fe0d06dae02470511c1d216959af10bdbc68e9fbf8b1b7751c70211000000050aca7173000000000000000000

1 output(s) for total of 388.556660284000 dcy

stealth address amount amount idx
00: 16fa86f9f2f5bac46792bb3bb3e790fe9e999ecc324df0e5e2fa0d94a179ed57 388.556660284000 110474 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": 59932, "vin": [ { "gen": { "height": 59922 } } ], "vout": [ { "amount": 388556660284, "target": { "key": "16fa86f9f2f5bac46792bb3bb3e790fe9e999ecc324df0e5e2fa0d94a179ed57" } } ], "extra": [ 1, 131, 102, 133, 153, 182, 158, 15, 224, 208, 109, 174, 2, 71, 5, 17, 193, 210, 22, 149, 154, 241, 11, 219, 198, 142, 159, 191, 139, 27, 119, 81, 199, 2, 17, 0, 0, 0, 5, 10, 202, 113, 115, 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