← previous blocknext block →recent activity
Analyzing
Block #87,518,536
11 transactions · 9 stateful · 2026-07-13 16:15:04 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,518,536 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xf69bf8bb…421f
0x34b655…2a6f
4 touches
1 conflict
0x7d99d945…e807
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc335872c…4214
0x34b655…2a6f
4 touches
1 conflict
0x02f0ef4a…7144
0x34b655…2a6f
2 touches
0 conflicts
0x0b65d0ba…a344
0x34b655…2a6f
2 touches
0 conflicts
0x0b65d0ba…a345
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
1 conflict on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity