Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7fa94f5c190ae63db81d6cbce07be2e267a4f99a52a10a9a40ca500b59a414

Tx prefix hash: e3c262c4badad381a27116c16a737117fb5da7199108269be7a75af87e48eafe
Tx public key: 515356b79a1a307c2ed7c8116bc92a1ab78c5b0ae50a6a2edd45eb37c9318664
Timestamp: 1762785531 Timestamp [UCT]: 2025-11-10 14:38:51 Age [y:d:h:m:s]: 00:042:23:29:58
Block: 1409142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30765 RingCT/type: yes/0
Extra: 01515356b79a1a307c2ed7c8116bc92a1ab78c5b0ae50a6a2edd45eb37c9318664021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d98dbf5122be38c0e088a6c0161c0694e4a59a5b64142e8950a427844e1764bb 0.600000000000 1897575 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": 1409152, "vin": [ { "gen": { "height": 1409142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d98dbf5122be38c0e088a6c0161c0694e4a59a5b64142e8950a427844e1764bb" } } ], "extra": [ 1, 81, 83, 86, 183, 154, 26, 48, 124, 46, 215, 200, 17, 107, 201, 42, 26, 183, 140, 91, 10, 229, 10, 106, 46, 221, 69, 235, 55, 201, 49, 134, 100, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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