← previous blocknext block →recent activity
Analyzing
Block #86,814,208
26 transactions · 24 stateful · 2026-07-10 09:45:36 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,814,208 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w18w010w111w013w214w315w418w120w221w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f1e40f…09a3
0x3bd359…433a
10 touches
10 conflicts
0x504ac60b…20a6
0x754704…b603
10 touches
10 conflicts
0x527f20e3…82e7
0x754704…b603
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0x55642f63…03d6
0x34b655…2a6f
4 touches
1 conflict
0x68edd6ac…8c3c
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Wrapped MON (WMON)
10 conflicts on slot 0xd9f1e40f03…3209a3
Audit this contract →
← previous block·next block →recent activity