← previous blocknext block →recent activity
Analyzing
Block #87,488,232
20 transactions · 15 stateful · 2026-07-13 12:52:08 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,488,232 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w29w313w414w515w619w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96bfa04d…d06b
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc2f84a16…86b8
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb568bd0a…0a72
0x34b655…2a6f
6 touches
3 conflicts
0x57c8db9d…3979
0x34b655…2a6f
6 touches
3 conflicts
0xb9266685…8b1d
0x34b655…2a6f
6 touches
3 conflicts
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 0x96bfa04d52…3ed06b
Audit this contract →
← previous block·next block →recent activity