Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ab7b8f41c5ad11f4b9cda8a10b889c8f294450e3970b474788955b45aba0a0

Tx prefix hash: f877e56d843136ec2bdad3c36d527bcdb773fdae25ef3c796eef65c50e5eea27
Tx public key: ada452573968db1a179e764fb78bf4c7a26056733b0d721d84afe7fd6944e97d
Timestamp: 1583849788 Timestamp [UCT]: 2020-03-10 14:16:28 Age [y:d:h:m:s]: 04:296:05:52:40
Block: 79690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106976 RingCT/type: yes/0
Extra: 01ada452573968db1a179e764fb78bf4c7a26056733b0d721d84afe7fd6944e97d02110000000128db8c57000000000000000000

1 output(s) for total of 334.160213326000 dcy

stealth address amount amount idx
00: aff6d786db9e076a20aaeb89a653720880ee57d647b8e6b1bc8208d5ffa221a3 334.160213326000 145842 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": 79700, "vin": [ { "gen": { "height": 79690 } } ], "vout": [ { "amount": 334160213326, "target": { "key": "aff6d786db9e076a20aaeb89a653720880ee57d647b8e6b1bc8208d5ffa221a3" } } ], "extra": [ 1, 173, 164, 82, 87, 57, 104, 219, 26, 23, 158, 118, 79, 183, 139, 244, 199, 162, 96, 86, 115, 59, 13, 114, 29, 132, 175, 231, 253, 105, 68, 233, 125, 2, 17, 0, 0, 0, 1, 40, 219, 140, 87, 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