← previous blocknext block →recent activity
Analyzing
Block #88,365,283
14 transactions · 12 stateful · 2026-07-17 14:40:27 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,365,283 · 14 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
1w04w15w27w38w311w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f900be0…cd6e
0x34b655…2a6f
6 touches
3 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0xea2d949b…9b29
0x34b655…2a6f
6 touches
3 conflicts
0x2f461725…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x314add6a…c880
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6630d365…74ad
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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 0x6f900be04d…4ccd6e
Audit this contract →
← previous block·next block →recent activity