← previous blocknext block →recent activity
Analyzing
Block #88,139,929
23 transactions · 17 stateful · 2026-07-16 13:31:55 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,139,929 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w010w012w013w114w217w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x572da21f…f703
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe2263bea…6a9d
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6aa0
0x2b46c0…1669
4 touches
1 conflict
0xed7dd7db…6022
0x2b46c0…1669
4 touches
1 conflict
0x0b6605df…08f8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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: Perpl
6 conflicts on slot 0x572da21f91…6af703
Audit this contract →
← previous block·next block →recent activity