← previous blocknext block →recent activity
Analyzing
Block #86,454,361
23 transactions · 17 stateful · 2026-07-08 17:38:36 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,454,361 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w012w313w021w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xe311ca08…f307
0x34b655…2a6f
6 touches
3 conflicts
0x3230277c…ef39
0xc8689a…ee79
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0xb1073fce…86ed
0x34b655…2a6f
4 touches
1 conflict
0xb39cb1d8…effa
0x34b655…2a6f
4 touches
1 conflict
0xbebeaa56…211b
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x000bde1afc…91e123
Audit this contract →
← previous block·next block →recent activity