Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31286eab20a851725905e883e1ad686ba3f5cdc11feb665e161d16d7f9a21468

Tx prefix hash: 747cc98b29b4b60646199e9c2f7a730d68b2dd4f08cc80093309cb9276a8d95e
Tx public key: 7b8911980b9f99cacdbc493cec781bc8b4cb4aee62989253508b5c9d3150e31f
Timestamp: 1751513385 Timestamp [UCT]: 2025-07-03 03:29:45 Age [y:d:h:m:s]: 00:129:15:25:01
Block: 1317665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90890 RingCT/type: yes/0
Extra: 017b8911980b9f99cacdbc493cec781bc8b4cb4aee62989253508b5c9d3150e31f021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d993fca2be51fe6c1c24729fc7f5c41b6e65a682cdba7b2cc4e66d708987d3de 0.600000000000 1805334 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": 1317675, "vin": [ { "gen": { "height": 1317665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d993fca2be51fe6c1c24729fc7f5c41b6e65a682cdba7b2cc4e66d708987d3de" } } ], "extra": [ 1, 123, 137, 17, 152, 11, 159, 153, 202, 205, 188, 73, 60, 236, 120, 27, 200, 180, 203, 74, 238, 98, 152, 146, 83, 80, 139, 92, 157, 49, 80, 227, 31, 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