← previous blocknext block →recent activity
Analyzing
Block #87,580,414
20 transactions · 16 stateful · 2026-07-13 23:09:29 UTC
Parallelism
50/100
Blocked
69%
Avg conflicts / tx
1.25
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,580,414 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w59w210w611w713w818w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x4ca5fbf0…6059
0x34b655…2a6f
6 touches
3 conflicts
0x41bc5f7b…26f2
0x34b655…2a6f
4 touches
1 conflict
0x5250e2f6…9390
0x34b655…2a6f
4 touches
1 conflict
0x57998639…d04d
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity