← previous blocknext block →recent activity
Analyzing
Block #87,056,374
10 transactions · 9 stateful · 2026-07-11 12:44:20 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,056,374 · 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
5w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1c8b4f85…d07d
0x34b655…2a6f
4 touches
1 conflict
0xdb88134d…d6c1
0x34b655…2a6f
4 touches
1 conflict
0xdb88134d…d6c2
0x34b655…2a6f
4 touches
1 conflict
0xe860e8c0…de9b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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
1 conflict on slot 0xc10b903def…412f54
Audit this contract →
← previous block·next block →recent activity