← previous blocknext block →recent activity
Analyzing
Block #86,735,860
21 transactions · 21 stateful · 2026-07-10 01:02:16 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,735,860 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w29w310w413w514w615w719w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc3f7ee8…7924
0x34b655…2a6f
8 touches
6 conflicts
0x4ae3b148…7ed2
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x1e6a4809…ebc8
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xcc3f7ee8e4…307924
Audit this contract →
← previous block·next block →recent activity