← previous blocknext block →recent activity
Analyzing
Block #86,978,237
21 transactions · 20 stateful · 2026-07-11 04:02:10 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,978,237 · 21 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
1w05w08w19w210w311w112w213w415w519w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x30aaa982…9d53
0x34b655…2a6f
6 touches
3 conflicts
0xa412324b…90aa
0x34b655…2a6f
6 touches
3 conflicts
0xa412324b…90ab
0x34b655…2a6f
6 touches
3 conflicts
0xd1db601b…c70d
0x34b655…2a6f
6 touches
3 conflicts
0x21683d77…4e07
0x34b655…2a6f
6 touches
3 conflicts
0xe9d235e0…3a43
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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity