← previous blocknext block →recent activity
Analyzing
Block #86,847,867
24 transactions · 21 stateful · 2026-07-10 13:30:45 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,847,867 · 24 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
1w02w13w26w07w18w29w310w013w214w115w417w318w420w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f42e42b…5717
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
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
6 conflicts on slot 0x6f42e42b3c…425717
Audit this contract →
← previous block·next block →recent activity