← previous blocknext block →recent activity
Analyzing
Block #86,798,000
21 transactions · 18 stateful · 2026-07-10 07:57:18 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,798,000 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w412w514w618w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x0b9f02c4…6fec
0x34b655…2a6f
12 touches
15 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf45f2405…c8f9
0x34b655…2a6f
6 touches
3 conflicts
0x7c7eff13…16db
0x34b655…2a6f
6 touches
3 conflicts
0xad432af7…e34f
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity