← previous blocknext block →recent activity
Analyzing
Block #87,670,232
24 transactions · 23 stateful · 2026-07-14 09:09:55 UTC
Parallelism
79/100
Blocked
26%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,670,232 · 24 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
1w09w010w111w215w317w120w422w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8f4deb0…dcf3
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb76f7c01…c3a5
0x34b655…2a6f
6 touches
3 conflicts
0xc948dbdc…199a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x536588d3…19c5
0x34b655…2a6f
6 touches
3 conflicts
0x8e8d48a4…7a75
0x34b655…2a6f
4 touches
1 conflict
0x8eedf936…a0c3
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 0xc8f4deb0cc…f2dcf3
Audit this contract →
← previous block·next block →recent activity