← previous blocknext block →recent activity
Analyzing
Block #87,690,070
19 transactions · 17 stateful · 2026-07-14 11:22:30 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,690,070 · 19 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
3w04w05w19w110w211w214w315w417w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf6de35e…bafd
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xb670a63e…ead8
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x99ee776a…053a
0x34b655…2a6f
6 touches
3 conflicts
0xb1b21ea8…d790
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641c
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
10 conflicts on slot 0xbf6de35e01…bfbafd
Audit this contract →
← previous block·next block →recent activity