Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4711cdbe146099c27c04a08b5644d5c867bbfb10da85d031b2a8470d8e308351

Tx prefix hash: 01eac0232d60a2205e7adf6172cfdb1e20383429d60fef08ac63d94fe9b67844
Tx public key: 42a99f4e912136218d361cae2f90347f0c45a83c6f353376bb67ea026928a7c6
Timestamp: 1755886719 Timestamp [UTC]: 2025-08-22 18:18:39 Age [y:d:h:m:s]: 01:089:23:16:43
Block: 1352155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330701 RingCT/type: yes/0
Extra: 0142a99f4e912136218d361cae2f90347f0c45a83c6f353376bb67ea026928a7c60211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ba64044e1cff4c604f0e5a12cc4062642040b31c5e1138c827c1781e7858910e 0.000600000000 1840118 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": 1352165, "vin": [ { "gen": { "height": 1352155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba64044e1cff4c604f0e5a12cc4062642040b31c5e1138c827c1781e7858910e" } } ], "extra": [ 1, 66, 169, 159, 78, 145, 33, 54, 33, 141, 54, 28, 174, 47, 144, 52, 127, 12, 69, 168, 60, 111, 53, 51, 118, 187, 103, 234, 2, 105, 40, 167, 198, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: