← previous blocknext block →recent activity
Analyzing
Block #88,363,994
19 transactions · 17 stateful · 2026-07-17 14:31:42 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,363,994 · 19 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
1w02w13w27w09w010w111w212w314w415w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x40856fd2…0eb9
0x34b655…2a6f
4 touches
1 conflict
0x42d5e8f3…5930
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x98e2e7cd…e4c2
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity