Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e34e595138df917507d3a2781a53a468ec4a2c89ec2c4cd463a184128b1c538

Tx prefix hash: cf304114dbb2b33648af3b712cca4fd64cdce497c7e507fdb36d4880fc066a1d
Tx public key: e3683fa26d5d8dd5afcf7e189d9a2bba5e1ba1eff69a5cd913cca13b708df483
Timestamp: 1710969111 Timestamp [UCT]: 2024-03-20 21:11:51 Age [y:d:h:m:s]: 01:087:19:39:21
Block: 982704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323665 RingCT/type: yes/0
Extra: 01e3683fa26d5d8dd5afcf7e189d9a2bba5e1ba1eff69a5cd913cca13b708df48302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dacb879fc9348c7ab4f8a1ae260ebcf1a82eb7e518f22831e9f8ebc1ac4c24a 0.600000000000 1442813 of 15

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": 982714, "vin": [ { "gen": { "height": 982704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dacb879fc9348c7ab4f8a1ae260ebcf1a82eb7e518f22831e9f8ebc1ac4c24a" } } ], "extra": [ 1, 227, 104, 63, 162, 109, 93, 141, 213, 175, 207, 126, 24, 157, 154, 43, 186, 94, 27, 161, 239, 246, 154, 92, 217, 19, 204, 161, 59, 112, 141, 244, 131, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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