← previous blocknext block →recent activity
Analyzing
Block #87,750,258
18 transactions · 16 stateful · 2026-07-14 18:05:30 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,750,258 · 18 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
4w05w16w27w310w011w412w513w516w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x1b9ea90e…c0f5
0x34b655…2a6f
10 touches
10 conflicts
0x0f00f2df…7579
0x34b655…2a6f
10 touches
10 conflicts
0xd4702f73…926c
0x34b655…2a6f
10 touches
10 conflicts
0x3fde350e…8d43
0x34b655…2a6f
10 touches
10 conflicts
0x91173b78…d64d
0x34b655…2a6f
9 touches
10 conflicts
0xe55dfce2…8d87
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity