← previous blocknext block →recent activity
Analyzing
Block #86,780,522
14 transactions · 13 stateful · 2026-07-10 06:00:37 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,780,522 · 14 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
4w05w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7f1d69b…384e
0x34b655…2a6f
4 touches
1 conflict
0x619281ca…b27d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x1f1d2c6e…6b63
0x34b655…2a6f
4 touches
1 conflict
0x1f1d2c6e…6b62
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xd591c69a…6721
0x34b655…2a6f
3 touches
1 conflict
0xba5743c7…21c1
0x1b6862…e19c
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 0xa7f1d69b72…07384e
Audit this contract →
← previous block·next block →recent activity