Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 031c141031662930f93bc4f67eb4126a45472947192e6a8316c603aeb2ce01f0

Tx prefix hash: c478353682a9e78c8b0c87b4fbba5a046b23e7fa75c743a0ffefee26ba62ce8a
Tx public key: d4bac60c0ae5d0aaad53762e1ee7681ac97d77e3dc15bfad8fdf1fc5b28ed289
Timestamp: 1644400249 Timestamp [UCT]: 2022-02-09 09:50:49 Age [y:d:h:m:s]: 03:021:09:44:15
Block: 434890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 795120 RingCT/type: yes/0
Extra: 01d4bac60c0ae5d0aaad53762e1ee7681ac97d77e3dc15bfad8fdf1fc5b28ed2890211000000025eb576c5000000000000000000

1 output(s) for total of 22.234593783000 dcy

stealth address amount amount idx
00: 85ee7ad2f3a3c4e886881432bea7919d6cc651799434a69425004f56e1703c3d 22.234593783000 845933 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": 434900, "vin": [ { "gen": { "height": 434890 } } ], "vout": [ { "amount": 22234593783, "target": { "key": "85ee7ad2f3a3c4e886881432bea7919d6cc651799434a69425004f56e1703c3d" } } ], "extra": [ 1, 212, 186, 198, 12, 10, 229, 208, 170, 173, 83, 118, 46, 30, 231, 104, 26, 201, 125, 119, 227, 220, 21, 191, 173, 143, 223, 31, 197, 178, 142, 210, 137, 2, 17, 0, 0, 0, 2, 94, 181, 118, 197, 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