← previous blocknext block →recent activity
Analyzing
Block #87,754,280
20 transactions · 18 stateful · 2026-07-14 18:32:24 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,754,280 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w19w210w311w413w214w315w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x9666da3b…0f0e
0x34b655…2a6f
6 touches
3 conflicts
0x3f798539…99c4
0x34b655…2a6f
4 touches
1 conflict
0x1896e05f…0421
0x34b655…2a6f
4 touches
1 conflict
0x709b98ea…4187
0x34b655…2a6f
4 touches
1 conflict
0x70b90757…51be
0x34b655…2a6f
4 touches
1 conflict
0x79bdf655…91f2
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity