← previous blocknext block →recent activity
Analyzing
Block #87,621,050
13 transactions · 11 stateful · 2026-07-14 03:41:13 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,621,050 · 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
2w03w16w07w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x220a8541…6431
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x18e900fa…07f4
0x34b655…2a6f
4 touches
1 conflict
0x1a73f7fe…9d8d
0x34b655…2a6f
4 touches
1 conflict
0x1fbab97c…79c7
0x34b655…2a6f
4 touches
1 conflict
0x2162732a…076e
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
3 conflicts on slot 0x220a8541a8…fb6431
Audit this contract →
← previous block·next block →recent activity