Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4e0942cb99332fe83fae5545110ce4ddebe87228b68480d2e779b0a94878f3e

Tx prefix hash: c06be646a8053c33b44a00ceaf6c7576d8db1204f121790e22f0be89f5a506ac
Tx public key: 18da521dcea3f61ecf4eea01ddd981bec1c5d367fe2f17039282db259fc8b2de
Timestamp: 1747534470 Timestamp [UTC]: 2025-05-18 02:14:30 Age [y:d:h:m:s]: 01:068:15:15:52
Block: 1285299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297815 RingCT/type: yes/0
Extra: 0118da521dcea3f61ecf4eea01ddd981bec1c5d367fe2f17039282db259fc8b2de02110000000601491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 05563f4cef4ef71256d179b623fd54171d0c6d110eaa1ea4ab6da04d9a129d58 0.000600000000 1772764 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": 1285309, "vin": [ { "gen": { "height": 1285299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05563f4cef4ef71256d179b623fd54171d0c6d110eaa1ea4ab6da04d9a129d58" } } ], "extra": [ 1, 24, 218, 82, 29, 206, 163, 246, 30, 207, 78, 234, 1, 221, 217, 129, 190, 193, 197, 211, 103, 254, 47, 23, 3, 146, 130, 219, 37, 159, 200, 178, 222, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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: