Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b26febb3dc61dca1c6a7c5f4df4a04339156ca351032a61caf56cdd4d0ee65

Tx prefix hash: 10f928e75d5a19620d648f57fa6c86c68a18d3b3ce81ce594aa20cc770e7d7b5
Tx public key: 7b28de6d3e84e69f61626ec869ca32f51bf2c6f70d5baa2943b2e63fa323fa48
Timestamp: 1583530370 Timestamp [UCT]: 2020-03-06 21:32:50 Age [y:d:h:m:s]: 04:363:07:53:36
Block: 77626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154108 RingCT/type: yes/0
Extra: 017b28de6d3e84e69f61626ec869ca32f51bf2c6f70d5baa2943b2e63fa323fa480211000000138a2ee0d9000000000000000000

1 output(s) for total of 339.463927315000 dcy

stealth address amount amount idx
00: 47a8c7c245edd4f5fccf83a24747454167db72a2fd455608295bba3ee0276621 339.463927315000 142773 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": 77636, "vin": [ { "gen": { "height": 77626 } } ], "vout": [ { "amount": 339463927315, "target": { "key": "47a8c7c245edd4f5fccf83a24747454167db72a2fd455608295bba3ee0276621" } } ], "extra": [ 1, 123, 40, 222, 109, 62, 132, 230, 159, 97, 98, 110, 200, 105, 202, 50, 245, 27, 242, 198, 247, 13, 91, 170, 41, 67, 178, 230, 63, 163, 35, 250, 72, 2, 17, 0, 0, 0, 19, 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