Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 642c9da3834c95072b2ed9a21a602116bc07be0c564119592a26a555c43a1797

Tx prefix hash: 7e6f9083c8e8f838bd61c3ed6c161d08769c55257789b07f2e5d217a01e2ccfc
Tx public key: b5a834a87d959c8ea780a28cb82a130600bec1a9dfb3f18f68b24be8dfa324dc
Timestamp: 1738073517 Timestamp [UCT]: 2025-01-28 14:11:57 Age [y:d:h:m:s]: 00:252:14:48:16
Block: 1206985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178232 RingCT/type: yes/0
Extra: 01b5a834a87d959c8ea780a28cb82a130600bec1a9dfb3f18f68b24be8dfa324dc021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4e89bcf1f0086d32a1e04d7fb4be683e8183527f981c61388fb12895386a7bb 0.600000000000 1693706 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": 1206995, "vin": [ { "gen": { "height": 1206985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4e89bcf1f0086d32a1e04d7fb4be683e8183527f981c61388fb12895386a7bb" } } ], "extra": [ 1, 181, 168, 52, 168, 125, 149, 156, 142, 167, 128, 162, 140, 184, 42, 19, 6, 0, 190, 193, 169, 223, 179, 241, 143, 104, 178, 75, 232, 223, 163, 36, 220, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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