← previous blocknext block →recent activity
Analyzing
Block #88,342,995
23 transactions · 22 stateful · 2026-07-17 12:10:37 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,342,995 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w38w312w114w415w522w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x18a3a88d…3c12
0x34b655…2a6f
6 touches
3 conflicts
0x38d36864…2cb0
0x34b655…2a6f
4 touches
1 conflict
0x3a996b35…bc8f
0x34b655…2a6f
4 touches
1 conflict
0x45542188…9e06
0x34b655…2a6f
4 touches
1 conflict
0x60520483…e2ef
0x34b655…2a6f
4 touches
1 conflict
0x6b11b9de…f60a
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 0x8252706a8a…797ca5
Audit this contract →
← previous block·next block →recent activity