← previous blocknext block →recent activity
Analyzing
Block #87,718,570
25 transactions · 23 stateful · 2026-07-14 14:33:32 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,718,570 · 25 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
3w05w08w19w213w014w315w117w322w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a1604d1…3e8a
0x34b655…2a6f
8 touches
6 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53355553…2976
0x34b655…2a6f
4 touches
1 conflict
0x722851f4…73fe
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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 0x6a1604d1a5…053e8a
Audit this contract →
← previous block·next block →recent activity