← previous blocknext block →recent activity
Analyzing
Block #87,877,164
20 transactions · 17 stateful · 2026-07-15 08:14:20 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,877,164 · 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
3w04w16w27w310w412w513w014w116w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb13b96bd…a3cb
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc5f336ca…912e
0x34b655…2a6f
6 touches
3 conflicts
0x0f6666e6…f280
0x34b655…2a6f
6 touches
3 conflicts
0xfd02114c…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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 0xb13b96bd5b…77a3cb
Audit this contract →
← previous block·next block →recent activity