← previous blocknext block →recent activity
Analyzing
Block #86,133,266
12 transactions · 9 stateful · 2026-07-07 05:54:09 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,133,266 · 12 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
6w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfcced5d…d3a0
0x34b655…2a6f
4 touches
1 conflict
0xb75d9839…c7bd
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x39181b59…1812
0x34b655…2a6f
2 touches
0 conflicts
0x4ce89478…7041
0x34b655…2a6f
2 touches
0 conflicts
0x59dbc306…f976
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 0xcfcced5dff…1bd3a0
Audit this contract →
← previous block·next block →recent activity