← previous blocknext block →recent activity
Analyzing
Block #86,809,794
20 transactions · 19 stateful · 2026-07-10 09:16:06 UTC
Parallelism
75/100
Blocked
26%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,809,794 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w312w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc40c8e2b…b832
0x34b655…2a6f
6 touches
3 conflicts
0xc7fed9f9…f3a0
0x34b655…2a6f
6 touches
3 conflicts
0x013c31f5…a717
0x34b655…2a6f
6 touches
3 conflicts
0x013c31f5…a718
0x34b655…2a6f
6 touches
3 conflicts
0x49a97bff…33ed
0x34b655…2a6f
4 touches
1 conflict
0x6f4c366d…04d2
0x34b655…2a6f
4 touches
1 conflict
0x833d2d11…e7ba
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity