Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9908a0c10e28d307bad41f7dca82f8eb0abc0646584de17c2f30725d3b339844

Tx prefix hash: bf83d9e00f7462211542c0417d7769a22594b9b8c9a55e2bb016bc94b5c807ae
Tx public key: bef71e869a78bfb3944131002da30e70aed0fedc7a8615e68e9d3f63e44bb483
Timestamp: 1730356218 Timestamp [UCT]: 2024-10-31 06:30:18 Age [y:d:h:m:s]: 00:058:02:54:43
Block: 1143333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41580 RingCT/type: yes/0
Extra: 01bef71e869a78bfb3944131002da30e70aed0fedc7a8615e68e9d3f63e44bb4830211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55525d24181f8e5b04a7100a0b21f075d35f3c8f61cc9b9cb26f5931457163f6 0.600000000000 1627196 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": 1143343, "vin": [ { "gen": { "height": 1143333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55525d24181f8e5b04a7100a0b21f075d35f3c8f61cc9b9cb26f5931457163f6" } } ], "extra": [ 1, 190, 247, 30, 134, 154, 120, 191, 179, 148, 65, 49, 0, 45, 163, 14, 112, 174, 208, 254, 220, 122, 134, 21, 230, 142, 157, 63, 99, 228, 75, 180, 131, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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