← previous blocknext block →recent activity
Analyzing
Block #86,988,314
11 transactions · 11 stateful · 2026-07-11 05:09:32 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,988,314 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa667abe…bdfc
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbf094cee…792f
0x34b655…2a6f
4 touches
1 conflict
0x43cea534…ddce
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
2 touches
0 conflicts
0x0178c2de…b37d
0xb1dbf0…c0d3
2 touches
0 conflicts
0x0335ae80…8414
0xb1dbf0…c0d3
2 touches
0 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
1 conflict on slot 0xfa667abe97…3ebdfc
Audit this contract →
← previous block·next block →recent activity