Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c9c395ddb86476b202d7d0d46a7929f57f058c0b274855cecb065acaef50892

Tx prefix hash: f7f0ff28cc777642a9655b304003adbae5bf41517f1fae4be2e21ecd914b0a8e
Tx public key: d13d674ddaf874fe82268659527f5f49aedeba691801a6b614ca66684b578cdc
Timestamp: 1577749791 Timestamp [UCT]: 2019-12-30 23:49:51 Age [y:d:h:m:s]: 05:135:19:07:04
Block: 35379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1246841 RingCT/type: yes/0
Extra: 01d13d674ddaf874fe82268659527f5f49aedeba691801a6b614ca66684b578cdc0211000000068a2ee0d9000000000000000000

1 output(s) for total of 468.571145014000 dcy

stealth address amount amount idx
00: 15646960c07afdc5319fe9105dc665c28d35b0dd8664cbe1e732b9f334a7f1bd 468.571145014000 59631 of 0

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": 35389, "vin": [ { "gen": { "height": 35379 } } ], "vout": [ { "amount": 468571145014, "target": { "key": "15646960c07afdc5319fe9105dc665c28d35b0dd8664cbe1e732b9f334a7f1bd" } } ], "extra": [ 1, 209, 61, 103, 77, 218, 248, 116, 254, 130, 38, 134, 89, 82, 127, 95, 73, 174, 222, 186, 105, 24, 1, 166, 182, 20, 202, 102, 104, 75, 87, 140, 220, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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