Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bc8e560e89d62998137261c4df78b75cd5c2788c570d674f3d399ce24cca895

Tx prefix hash: a290c2fc35d50512fe3f094bd9b2c26c9a03940466efe7fe342609743da6f262
Tx public key: 2a766f8401d6c6797c3367c29322731e0598fab91b59c6fee169300518b30c7e
Timestamp: 1735718291 Timestamp [UCT]: 2025-01-01 07:58:11 Age [y:d:h:m:s]: 00:092:18:09:46
Block: 1187732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66075 RingCT/type: yes/0
Extra: 012a766f8401d6c6797c3367c29322731e0598fab91b59c6fee169300518b30c7e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e86e31428d4f3c2618922a8cd6cab4fb764d61eaa431727dd8c93b73a9e1ecbb 0.600000000000 1674225 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": 1187742, "vin": [ { "gen": { "height": 1187732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e86e31428d4f3c2618922a8cd6cab4fb764d61eaa431727dd8c93b73a9e1ecbb" } } ], "extra": [ 1, 42, 118, 111, 132, 1, 214, 198, 121, 124, 51, 103, 194, 147, 34, 115, 30, 5, 152, 250, 185, 27, 89, 198, 254, 225, 105, 48, 5, 24, 179, 12, 126, 2, 17, 0, 0, 0, 3, 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