← previous blocknext block →recent activity
Analyzing
Block #86,830,193
18 transactions · 14 stateful · 2026-07-10 11:32:39 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,830,193 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w19w211w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac35341e…53e8
0x34b655…2a6f
6 touches
3 conflicts
0x4be9812b…48a9
0x34b655…2a6f
6 touches
3 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0x0e4000ee…afb9
0x34b655…2a6f
4 touches
1 conflict
0x3b689fd2…629c
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0xac35341e4d…7d53e8
Audit this contract →
← previous block·next block →recent activity