Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030425ed27f4c23dc27bcad769c07212cbf6bf2ad2d9c50f85fe3cd2dd703565

Tx prefix hash: 552cb71f73e9a937bd4e86a81ac5fac0821ce8f8a8068bdb2c138aac5f193027
Tx public key: 97e334016924d426e39dce8f48bed353578f327a5b74809ab6b4ac6dd63d42d1
Timestamp: 1744097690 Timestamp [UTC]: 2025-04-08 07:34:50 Age [y:d:h:m:s]: 01:225:08:49:25
Block: 1256829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425180 RingCT/type: yes/0
Extra: 0197e334016924d426e39dce8f48bed353578f327a5b74809ab6b4ac6dd63d42d1021100000005dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 499914e338705bb241edbd57d40936bcf91a431102b79e1a5e29d1e3bf59fc29 0.000600000000 1743946 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": 1256839, "vin": [ { "gen": { "height": 1256829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "499914e338705bb241edbd57d40936bcf91a431102b79e1a5e29d1e3bf59fc29" } } ], "extra": [ 1, 151, 227, 52, 1, 105, 36, 212, 38, 227, 157, 206, 143, 72, 190, 211, 83, 87, 143, 50, 122, 91, 116, 128, 154, 182, 180, 172, 109, 214, 61, 66, 209, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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: