← previous blocknext block →recent activity
Analyzing
Block #87,877,840
20 transactions · 18 stateful · 2026-07-15 08:18:51 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,877,840 · 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
4w05w17w28w311w412w517w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a8dad6e…4fe6
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
8 touches
6 conflicts
0xf66fdca9…90ab
0x34b655…2a6f
6 touches
3 conflicts
0x1291fef6…11a3
0x34b655…2a6f
6 touches
3 conflicts
0x38948e75…437a
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 0x3a8dad6ec9…934fe6
Audit this contract →
← previous block·next block →recent activity