← previous blocknext block →recent activity
Analyzing
Block #87,418,287
13 transactions · 10 stateful · 2026-07-13 05:04:31 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,418,287 · 13 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf907a0c…f7da
0x34b655…2a6f
4 touches
1 conflict
0xf62c017d…e543
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x6045a1eb…189e
0x34b655…2a6f
4 touches
1 conflict
0x0db25069…2fd1
0x34b655…2a6f
2 touches
0 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
2 touches
0 conflicts
0x22af2e4e…609c
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 0xcf907a0ced…ddf7da
Audit this contract →
← previous block·next block →recent activity