← previous blocknext block →recent activity
Analyzing
Block #86,979,245
19 transactions · 17 stateful · 2026-07-11 04:08:54 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,979,245 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w08w19w210w311w412w515w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2356194c…0d6b
0x34b655…2a6f
6 touches
3 conflicts
0x313d3d93…4aa2
0x34b655…2a6f
6 touches
3 conflicts
0x6a6e42c5…9438
0x34b655…2a6f
6 touches
3 conflicts
0x7ae44958…8593
0x34b655…2a6f
6 touches
3 conflicts
0x008accc4…1da7
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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity