← previous blocknext block →recent activity
Analyzing
Block #87,052,929
10 transactions · 9 stateful · 2026-07-11 12:21:15 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,052,929 · 10 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x013c31f5…a717
0x34b655…2a6f
4 touches
1 conflict
0x013c31f5…a718
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc7fed9f9…f3a0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
0x34b655…2a6f
2 touches
0 conflicts
0x79ace5b6…8d37
0x34b655…2a6f
2 touches
0 conflicts
0x823a3658…acf6
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 0x013c31f575…6ba717
Audit this contract →
← previous block·next block →recent activity