← previous blocknext block →recent activity
Analyzing
Block #87,578,247
13 transactions · 12 stateful · 2026-07-13 22:55:00 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,578,247 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x16dd4651…e88f
0x34b655…2a6f
4 touches
1 conflict
0x2170bea4…4722
0x34b655…2a6f
4 touches
1 conflict
0x2170bea4…4723
0x34b655…2a6f
4 touches
1 conflict
0x28fd6666…1287
0x34b655…2a6f
4 touches
1 conflict
0x2f702750…347d
0x34b655…2a6f
4 touches
1 conflict
0x313d3d93…4aa2
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