← previous blocknext block →recent activity
Analyzing
Block #88,807,076
20 transactions · 20 stateful · 2026-07-19 15:56:03 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,807,076 · 20 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
5w06w07w19w210w311w412w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046740ca…4065
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x2029b74e…c206
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x6dfec1b4…a745
0x34b655…2a6f
5 touches
3 conflicts
0x11a92863…5e7f
0x34b655…2a6f
5 touches
3 conflicts
0x5110a94f…86d2
0x34b655…2a6f
4 touches
1 conflict
0x64158499…e370
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
3 conflicts on slot 0x046740cacc…b84065
Audit this contract →
← previous block·next block →recent activity