← previous blocknext block →recent activity
Analyzing
Block #86,702,524
24 transactions · 19 stateful · 2026-07-09 21:19:36 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,702,524 · 24 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
7w08w19w210w311w412w113w515w016w120w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x2c226701…ff54
0x34b655…2a6f
6 touches
3 conflicts
0x2ff44d76…33d6
0x34b655…2a6f
6 touches
3 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 conflicts
0x6ef574aa…c1a7
0x34b655…2a6f
6 touches
3 conflicts
0x70ff9262…8d80
0x34b655…2a6f
6 touches
3 conflicts
0xa2e89145…7dfa
0x34b655…2a6f
6 touches
3 conflicts
0xa3da8ade…8ed5
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity