← previous blocknext block →recent activity
Analyzing
Block #86,789,354
11 transactions · 8 stateful · 2026-07-10 06:59:34 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,789,354 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x1b72fe29…aa90
0x34b655…2a6f
3 touches
1 conflict
0x0153d4c5…e644
0x34b655…2a6f
2 touches
0 conflicts
0x07f86c56…7736
0x34b655…2a6f
2 touches
0 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x6d148b57…bc8f
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 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity