Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a621f8e88f4fe9eaab2ea6f951f24ccbc6ba4b45eb85fcf14485075ac983cfa

Tx prefix hash: dd2584d0352f9b985fd14286695d0411ea43a5e1758e06f81fcf16e8ab654c32
Tx public key: 98a14fbd4c6c25b4b2dd34850123877aab58f0d4559544368e7d739f920ca7bb
Timestamp: 1764716351 Timestamp [UCT]: 2025-12-02 22:59:11 Age [y:d:h:m:s]: 00:001:03:48:50
Block: 1425154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 820 RingCT/type: yes/0
Extra: 0198a14fbd4c6c25b4b2dd34850123877aab58f0d4559544368e7d739f920ca7bb021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eabc9c5191ec4f79ebfcae48da214eef1ff2bdbdc3dcc3fca6d44ad5cb1e6ae2 0.600000000000 1913787 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": 1425164, "vin": [ { "gen": { "height": 1425154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eabc9c5191ec4f79ebfcae48da214eef1ff2bdbdc3dcc3fca6d44ad5cb1e6ae2" } } ], "extra": [ 1, 152, 161, 79, 189, 76, 108, 37, 180, 178, 221, 52, 133, 1, 35, 135, 122, 171, 88, 240, 212, 85, 149, 68, 54, 142, 125, 115, 159, 146, 12, 167, 187, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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