← previous blocknext block →recent activity
Analyzing
Block #88,139,771
22 transactions · 20 stateful · 2026-07-16 13:30:52 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,139,771 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w111w212w313w314w416w520w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
10 touches
10 conflicts
0x9465204c…bf37
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x4f473983…7d27
0x34b655…2a6f
8 touches
6 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4a3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity