← previous blocknext block →recent activity
Analyzing
Block #87,705,946
24 transactions · 23 stateful · 2026-07-14 13:08:54 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,705,946 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w09w311w013w114w215w318w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xd17b3c64…e8fa
0xd32edf…ff58
7 touches
6 conflicts
0x7a916b05…8a00
0x34b655…2a6f
6 touches
3 conflicts
0xab406501…39ee
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0xe741c135…25a9
0x34b655…2a6f
6 touches
3 conflicts
0xee4fe1f7…3ead
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity