← previous blocknext block →recent activity
Analyzing
Block #87,407,904
12 transactions · 12 stateful · 2026-07-13 03:55:02 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,407,904 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x34731dbd…e467
0x34b655…2a6f
6 touches
3 conflicts
0x1f6f8ff8…a5d4
0x34b655…2a6f
4 touches
1 conflict
0x1f6f8ff8…a5d5
0x34b655…2a6f
4 touches
1 conflict
0x37ab49be…3b8b
0x34b655…2a6f
4 touches
1 conflict
0x59c89f2b…2f10
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity