← previous blocknext block →recent activity
Analyzing
Block #86,834,147
14 transactions · 11 stateful · 2026-07-10 11:59:07 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,834,147 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x226e3b61…5e6f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc92cdb89…7078
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x05975727…7fcf
0x34b655…2a6f
4 touches
1 conflict
0x05e91261…0580
0x34b655…2a6f
2 touches
0 conflicts
0x09e78101…dad5
0x34b655…2a6f
2 touches
0 conflicts
0x0a6a5b44…d0e5
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 0x226e3b614e…db5e6f
Audit this contract →
← previous block·next block →recent activity