← previous blocknext block →recent activity
Analyzing
Block #87,661,005
21 transactions · 19 stateful · 2026-07-14 08:08:15 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,661,005 · 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
1w02w13w26w07w110w211w312w313w417w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ce640b…884a
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa4546b58…5322
0xd32edf…ff58
7 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc514314c…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0x64687417…8d60
0x34b655…2a6f
6 touches
3 conflicts
0x48315f67…c1a6
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 0x69ce640b96…ed884a
Audit this contract →
← previous block·next block →recent activity