← previous blocknext block →recent activity
Analyzing
Block #86,532,272
11 transactions · 11 stateful · 2026-07-09 02:19:08 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,532,272 · 11 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
1w06w17w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79dd653b…fd0f
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x48b3f8d0…4510
0x34b655…2a6f
2 touches
0 conflicts
0x64ae2aeb…442e
0x34b655…2a6f
2 touches
0 conflicts
0x7d2645cd…5d8e
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 0x79dd653b86…27fd0f
Audit this contract →
← previous block·next block →recent activity