← previous blocknext block →recent activity
Analyzing
Block #86,905,710
10 transactions · 9 stateful · 2026-07-10 19:57:37 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,905,710 · 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
1w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd526b516…a51a
0x34b655…2a6f
4 touches
1 conflict
0x64852187…6cb0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa0bc9ef1…59a0
0x34b655…2a6f
4 touches
1 conflict
0xb1e4ea6c…3e29
0x34b655…2a6f
4 touches
1 conflict
0xba639250…76be
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 0xd526b51665…59a51a
Audit this contract →
← previous block·next block →recent activity