Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a175fe93e2b1a25c3c2e3c9e6503d8ff7f56548a659a3fdb046d490c1a7c002

Tx prefix hash: ddfeb900f0df67f39a6ab4e89dab4df2b94fc80ba29186c7aed7d11a6051d02e
Tx public key: d443ae2020fe8ca37a5afbdc49c4a286503bad841cc3719b83f2fa84ac81d807
Timestamp: 1709080891 Timestamp [UCT]: 2024-02-28 00:41:31 Age [y:d:h:m:s]: 01:047:19:56:20
Block: 967038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295195 RingCT/type: yes/0
Extra: 01d443ae2020fe8ca37a5afbdc49c4a286503bad841cc3719b83f2fa84ac81d80702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51889f96ca6dd6b9e13aace905f66aedc30efce9e83eb8dc9dd8deb0739263a3 0.600000000000 1426809 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": 967048, "vin": [ { "gen": { "height": 967038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51889f96ca6dd6b9e13aace905f66aedc30efce9e83eb8dc9dd8deb0739263a3" } } ], "extra": [ 1, 212, 67, 174, 32, 32, 254, 140, 163, 122, 90, 251, 220, 73, 196, 162, 134, 80, 59, 173, 132, 28, 195, 113, 155, 131, 242, 250, 132, 172, 129, 216, 7, 2, 17, 0, 0, 0, 2, 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