Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5205d68f3f24b540a7678175ba4f066aa608dccc4ed75f6318541a115721668a

Tx prefix hash: 1e34ee7402bc0709e6ed96d76df2360494c7021c1447cb7088a2ae6700f6b380
Tx public key: 322a9fb9739f1f7f7af2214d25e9062f760f95cb0d7f8010207521503d527171
Timestamp: 1751680852 Timestamp [UCT]: 2025-07-05 02:00:52 Age [y:d:h:m:s]: 00:133:16:50:43
Block: 1318976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93877 RingCT/type: yes/0
Extra: 01322a9fb9739f1f7f7af2214d25e9062f760f95cb0d7f8010207521503d52717102110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25bb516e02382f86e6d7eeb88e9485b13b306dfec3d3630adf30037d49a1a8c3 0.600000000000 1806665 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": 1318986, "vin": [ { "gen": { "height": 1318976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25bb516e02382f86e6d7eeb88e9485b13b306dfec3d3630adf30037d49a1a8c3" } } ], "extra": [ 1, 50, 42, 159, 185, 115, 159, 31, 127, 122, 242, 33, 77, 37, 233, 6, 47, 118, 15, 149, 203, 13, 127, 128, 16, 32, 117, 33, 80, 61, 82, 113, 113, 2, 17, 0, 0, 0, 1, 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