← previous blocknext block →recent activity
Analyzing
Block #87,408,434
10 transactions · 8 stateful · 2026-07-13 03:58:34 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,408,434 · 10 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
1w02w13w26w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xceb535f3…19cf
0x34b655…2a6f
6 touches
3 conflicts
0xd1fe26e6…8d31
0x34b655…2a6f
6 touches
3 conflicts
0xc1aad6e5…9135
0x34b655…2a6f
6 touches
3 conflicts
0x34528a3a…a6d6
0x34b655…2a6f
6 touches
3 conflicts
0x4a5dac02…9503
0x34b655…2a6f
4 touches
1 conflict
0x4da995bd…d5ef
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x69ce640b…884a
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 0xceb535f356…6319cf
Audit this contract →
← previous block·next block →recent activity