Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a50f58c5c7addf97f77798fdd9c9223312ce0df5f6b35a29482defa6f6664183

Tx prefix hash: 9f8cbdc425a73e439519cc239dcd955f13421738081467f44041e13f60bdee22
Tx public key: 21852f3b1544b2f0a674130609020a5aeb0f9bb03e80a7e2eef8a70a79a01eeb
Timestamp: 1751488768 Timestamp [UCT]: 2025-07-02 20:39:28 Age [y:d:h:m:s]: 00:132:06:23:30
Block: 1317461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92766 RingCT/type: yes/0
Extra: 0121852f3b1544b2f0a674130609020a5aeb0f9bb03e80a7e2eef8a70a79a01eeb02110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e525ba499d138a93b5e65dc46ca453b48dae77a4a68623e09c88778ada7584d 0.600000000000 1805128 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": 1317471, "vin": [ { "gen": { "height": 1317461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e525ba499d138a93b5e65dc46ca453b48dae77a4a68623e09c88778ada7584d" } } ], "extra": [ 1, 33, 133, 47, 59, 21, 68, 178, 240, 166, 116, 19, 6, 9, 2, 10, 90, 235, 15, 155, 176, 62, 128, 167, 226, 238, 248, 167, 10, 121, 160, 30, 235, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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