← previous blocknext block →recent activity
Analyzing
Block #86,982,802
23 transactions · 22 stateful · 2026-07-11 04:32:42 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,982,802 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w19w010w111w112w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
4 touches
1 conflict
0x1f38d034…f304
0x34b655…2a6f
4 touches
1 conflict
0x37773728…f3a4
0x34b655…2a6f
4 touches
1 conflict
0x3adc2445…f1f2
0x34b655…2a6f
4 touches
1 conflict
0x68181199…14e6
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity