← previous blocknext block →recent activity
Analyzing
Block #87,355,879
22 transactions · 20 stateful · 2026-07-12 22:07:03 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,355,879 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w512w115w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x1e48811e…2e39
0x34b655…2a6f
6 touches
3 conflicts
0x239122db…dc81
0x34b655…2a6f
6 touches
3 conflicts
0x18ec97d9…6baa
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
6 touches
3 conflicts
0xe2307994…acad
0x34b655…2a6f
6 touches
3 conflicts
0x5ba51e87…44ee
0xb1dbf0…c0d3
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