Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a31e761a4cb63bde5f3a60cc8e98a38eb722e3528d84d29e35d7e54a619a94f

Tx prefix hash: 818d6f13bac65ea2f4253bb94cbfee225569cb3f15c9d35142b067977702d35b
Tx public key: 6682a0f8bae48961e378b3b5532fd3391d4475774e62c7a76cb8a02eef84efd8
Timestamp: 1743880558 Timestamp [UTC]: 2025-04-05 19:15:58 Age [y:d:h:m:s]: 01:034:07:54:38
Block: 1255035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275766 RingCT/type: yes/0
Extra: 016682a0f8bae48961e378b3b5532fd3391d4475774e62c7a76cb8a02eef84efd80211000000046c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dba2fdd554d8fb23f1e02a36618f4a27fe914f1110a4dba0ff69f576598f2351 0.000600000000 1742136 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": 1255045, "vin": [ { "gen": { "height": 1255035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dba2fdd554d8fb23f1e02a36618f4a27fe914f1110a4dba0ff69f576598f2351" } } ], "extra": [ 1, 102, 130, 160, 248, 186, 228, 137, 97, 227, 120, 179, 181, 83, 47, 211, 57, 29, 68, 117, 119, 78, 98, 199, 167, 108, 184, 160, 46, 239, 132, 239, 216, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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: