Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2b35906edaf22c0928f700875f826c5ad5cfbaa6e7abaa96fc0c558f75f8265

Tx prefix hash: 10b3f109adf3d05a47898a62665d9eb5ca2dfe63802fa7e6081b4f85275005f4
Tx public key: 7711e0ce2293d3cc328c45c93acbad017840ca31cf6920d5514a9ac5086d7b28
Timestamp: 1581819321 Timestamp [UCT]: 2020-02-16 02:15:21 Age [y:d:h:m:s]: 05:039:01:01:55
Block: 65669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181022 RingCT/type: yes/0
Extra: 017711e0ce2293d3cc328c45c93acbad017840ca31cf6920d5514a9ac5086d7b280211000000018a2ee0d9000000000000000000

1 output(s) for total of 371.887989433000 dcy

stealth address amount amount idx
00: ad8f9cede97cb9f2888690e667306f11c544f4ea35f82072a50d0c0f65c173db 371.887989433000 121206 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": 65679, "vin": [ { "gen": { "height": 65669 } } ], "vout": [ { "amount": 371887989433, "target": { "key": "ad8f9cede97cb9f2888690e667306f11c544f4ea35f82072a50d0c0f65c173db" } } ], "extra": [ 1, 119, 17, 224, 206, 34, 147, 211, 204, 50, 140, 69, 201, 58, 203, 173, 1, 120, 64, 202, 49, 207, 105, 32, 213, 81, 74, 154, 197, 8, 109, 123, 40, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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