Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88e559fce0269db16ba9040f5804a3be7a0e4d7fd808083642ec8dd87d036df7

Tx prefix hash: c7655fee2ce240660ae8774aa9f02e29411983a0b3eb043af9e2d9e5450d6474
Tx public key: 18d255b8b7b562c9686477d63d419972f19a389537582fbe9c07a11c59d32f8c
Timestamp: 1716082553 Timestamp [UCT]: 2024-05-19 01:35:53 Age [y:d:h:m:s]: 00:304:21:47:16
Block: 1025082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217949 RingCT/type: yes/0
Extra: 0118d255b8b7b562c9686477d63d419972f19a389537582fbe9c07a11c59d32f8c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1a725018600e724915a346ff06b0b3308ea22ce5ce925b88714f9cc338c7dc7 0.600000000000 1491325 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": 1025092, "vin": [ { "gen": { "height": 1025082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1a725018600e724915a346ff06b0b3308ea22ce5ce925b88714f9cc338c7dc7" } } ], "extra": [ 1, 24, 210, 85, 184, 183, 181, 98, 201, 104, 100, 119, 214, 61, 65, 153, 114, 241, 154, 56, 149, 55, 88, 47, 190, 156, 7, 161, 28, 89, 211, 47, 140, 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