Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af1f91faf6d00f9b936cb8b11bedde6154b03fbf926503f9b8d850e1d570ac8e

Tx prefix hash: e2b44ad3bccb1216c215426bb64b1f2fc2b3f041ae66588a6b3303ab67170229
Tx public key: ec4c8ace5d0e90da26c16f53f4d8cf89771baa50d1d1466aeb36e79fe3cb2d0d
Timestamp: 1773038881 Timestamp [UTC]: 2026-03-09 06:48:01 Age [y:d:h:m:s]: 00:257:19:26:54
Block: 1493897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189597 RingCT/type: yes/0
Extra: 01ec4c8ace5d0e90da26c16f53f4d8cf89771baa50d1d1466aeb36e79fe3cb2d0d021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5cad24da81e09dcb74172e1b1d94a10b32077aca19057d4751295b6d0d6a2912 0.000600000000 1983463 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": 1493907, "vin": [ { "gen": { "height": 1493897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cad24da81e09dcb74172e1b1d94a10b32077aca19057d4751295b6d0d6a2912" } } ], "extra": [ 1, 236, 76, 138, 206, 93, 14, 144, 218, 38, 193, 111, 83, 244, 216, 207, 137, 119, 27, 170, 80, 209, 209, 70, 106, 235, 54, 231, 159, 227, 203, 45, 13, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: