← previous blocknext block →recent activity
Analyzing
Block #86,620,912
36 transactions · 25 stateful · 2026-07-09 12:13:25 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,620,912 · 36 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
5w06w17w28w319w020w121w222w323w424w025w328w030w134w135w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xda46a376…f6a6
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 conflicts
0x3230277c…ef39
0xc8689a…ee79
6 touches
3 conflicts
0x213ee207…a151
0x69df8a…6292
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity