← previous blocknext block →recent activity
Analyzing
Block #86,987,424
33 transactions · 25 stateful · 2026-07-11 05:03:34 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,987,424 · 33 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
2w07w111w215w017w121w023w224w125w226w328w330w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45877cba…0b50
0x34b655…2a6f
8 touches
6 conflicts
0x5768046f…c290
0xd32edf…ff58
5 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
0x34b655…2a6f
4 touches
1 conflict
0x86f32276…0ebf
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xef5838dd…00a4
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 0x45877cbaf8…d30b50
Audit this contract →
← previous block·next block →recent activity