← previous blocknext block →recent activity
Analyzing
Block #87,304,421
12 transactions · 9 stateful · 2026-07-12 16:22:57 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,304,421 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ee13be7…7b2c
0x34b655…2a6f
6 touches
3 conflicts
0xa9f59232…f58c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50e
0x34b655…2a6f
2 touches
0 conflicts
0x145b9bbf…e50f
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x0ee13be714…dc7b2c
Audit this contract →
← previous block·next block →recent activity