Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73f7d95cf4e8871edc3aa270f4e87ebff0da2bb8a2e35f7f99379d752e15adf4

Tx prefix hash: 24d72efde4a327d5b47d48a298731f7b659362bd4524c9e21d49b2a4ebab7351
Tx public key: 1244b9ccd86407409eb78341c39e60a273df513e1fcb05cd8aab923c366fbc0e
Timestamp: 1708636945 Timestamp [UCT]: 2024-02-22 21:22:25 Age [y:d:h:m:s]: 01:059:09:20:54
Block: 963347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303478 RingCT/type: yes/0
Extra: 011244b9ccd86407409eb78341c39e60a273df513e1fcb05cd8aab923c366fbc0e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf493e45712db4117b60ce81641c4debc47c3b9378330ef8597750671f63a429 0.600000000000 1423048 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": 963357, "vin": [ { "gen": { "height": 963347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf493e45712db4117b60ce81641c4debc47c3b9378330ef8597750671f63a429" } } ], "extra": [ 1, 18, 68, 185, 204, 216, 100, 7, 64, 158, 183, 131, 65, 195, 158, 96, 162, 115, 223, 81, 62, 31, 203, 5, 205, 138, 171, 146, 60, 54, 111, 188, 14, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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