Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad20bcdad61c6f914055c15d10f53946f5b5af95f12b7219a64a21a4d3d63666

Tx prefix hash: a7949a09183b7d4e7a3bed1d9be808f515505bfaeaf9f375fa6e32bef60dfbaf
Tx public key: 708b25cf5d51ed7dc708b65945643538202712bd435c39af9253c929c4c5ed24
Timestamp: 1617630747 Timestamp [UCT]: 2021-04-05 13:52:27 Age [y:d:h:m:s]: 03:267:20:41:35
Block: 233766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 951188 RingCT/type: yes/0
Extra: 01708b25cf5d51ed7dc708b65945643538202712bd435c39af9253c929c4c5ed240211000000239c1fbdcc000000000000000000

1 output(s) for total of 103.147641821000 dcy

stealth address amount amount idx
00: fdaaf945d272b3bb1c8ec2072de8644e72f1c5bfa10d5da59a4f4aeff7145f96 103.147641821000 485370 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": 233776, "vin": [ { "gen": { "height": 233766 } } ], "vout": [ { "amount": 103147641821, "target": { "key": "fdaaf945d272b3bb1c8ec2072de8644e72f1c5bfa10d5da59a4f4aeff7145f96" } } ], "extra": [ 1, 112, 139, 37, 207, 93, 81, 237, 125, 199, 8, 182, 89, 69, 100, 53, 56, 32, 39, 18, 189, 67, 92, 57, 175, 146, 83, 201, 41, 196, 197, 237, 36, 2, 17, 0, 0, 0, 35, 156, 31, 189, 204, 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