← previous blocknext block →recent activity
Analyzing
Block #86,961,603
21 transactions · 20 stateful · 2026-07-11 02:11:04 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,961,603 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w310w011w012w114w215w316w417w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x8eb11fc4…09b5
0xd32edf…ff58
9 touches
10 conflicts
0xa112f315…1a92
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x3be33cca…0fff
0x34b655…2a6f
6 touches
3 conflicts
0x3be33cca…1000
0x34b655…2a6f
6 touches
3 conflicts
0x7634a3f4…7f24
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity