Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2f2373f2b4d36d0508b4ace466e50f205e87ba5e7585c73cfc32dd2930b3214

Tx prefix hash: f1b46dc3ee7ce6f81b7bc41420cb01890c2d6e8d2629b97c6459ea96696d4e9d
Tx public key: 2cde77d3d1afa04bab9a3ea7274a0a475a67640906e02e135781a95cd75008d4
Timestamp: 1759093517 Timestamp [UTC]: 2025-09-28 21:05:17 Age [y:d:h:m:s]: 01:048:20:43:27
Block: 1378537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301263 RingCT/type: yes/0
Extra: 012cde77d3d1afa04bab9a3ea7274a0a475a67640906e02e135781a95cd75008d4021100000002a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f9c0e5b72b39e5edfff304fdb65ab1db59bae67d84f4f0a3bbab7393cc80e5e1 0.000600000000 1866632 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 dinastycoin-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": 1378547, "vin": [ { "gen": { "height": 1378537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9c0e5b72b39e5edfff304fdb65ab1db59bae67d84f4f0a3bbab7393cc80e5e1" } } ], "extra": [ 1, 44, 222, 119, 211, 209, 175, 160, 75, 171, 154, 62, 167, 39, 74, 10, 71, 90, 103, 100, 9, 6, 224, 46, 19, 87, 129, 169, 92, 215, 80, 8, 212, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: