Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcb98f3095fe0eb54eb0a20dc403b17b974ed37565a4cc56e5cd61c71a34ee2f

Tx prefix hash: b2ea942bb6578d61db8486d2e1dedbc4e438acaf35b8f4cc98e93a3f2e4b4449
Tx public key: a57a3cf5b3d4dcece1668a2281d43feca883e9501f4b0a80f5eb8b02a6cb14a2
Timestamp: 1749878619 Timestamp [UTC]: 2025-06-14 05:23:39 Age [y:d:h:m:s]: 00:342:04:47:41
Block: 1304622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235778 RingCT/type: yes/0
Extra: 01a57a3cf5b3d4dcece1668a2281d43feca883e9501f4b0a80f5eb8b02a6cb14a2021100000015bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0eb6942e426c69072f9a10867d46de8d148d57ce14d696d0d2935c3eda01ed74 0.000600000000 1792213 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": 1304632, "vin": [ { "gen": { "height": 1304622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eb6942e426c69072f9a10867d46de8d148d57ce14d696d0d2935c3eda01ed74" } } ], "extra": [ 1, 165, 122, 60, 245, 179, 212, 220, 236, 225, 102, 138, 34, 129, 212, 63, 236, 168, 131, 233, 80, 31, 75, 10, 128, 245, 235, 139, 2, 166, 203, 20, 162, 2, 17, 0, 0, 0, 21, 191, 81, 178, 162, 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: