Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 023c59703fa3935efab29ea5f2761acd9c1e434e85ef936992ac6e81392eba13

Tx prefix hash: 216f598a8796514ec997045afd08cc4b71cdb741800a5ec5f53d2c7fac6eb766
Tx public key: fc902edda8a12a023a2b56fef81ac71528ca24f87ae33498fc9ff1d32d535d00
Timestamp: 1577809444 Timestamp [UCT]: 2019-12-31 16:24:04 Age [y:d:h:m:s]: 04:306:07:48:28
Block: 35882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107983 RingCT/type: yes/0
Extra: 01fc902edda8a12a023a2b56fef81ac71528ca24f87ae33498fc9ff1d32d535d0002110000006ec5b5978f000000000000000000

1 output(s) for total of 466.776402301000 dcy

stealth address amount amount idx
00: 8b0c4ef32e615859296aaecb798aaf15710252b78c7a8f69c7d91aa09104b184 466.776402301000 60594 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": 35892, "vin": [ { "gen": { "height": 35882 } } ], "vout": [ { "amount": 466776402301, "target": { "key": "8b0c4ef32e615859296aaecb798aaf15710252b78c7a8f69c7d91aa09104b184" } } ], "extra": [ 1, 252, 144, 46, 221, 168, 161, 42, 2, 58, 43, 86, 254, 248, 26, 199, 21, 40, 202, 36, 248, 122, 227, 52, 152, 252, 159, 241, 211, 45, 83, 93, 0, 2, 17, 0, 0, 0, 110, 197, 181, 151, 143, 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