← previous blocknext block →recent activity
Analyzing
Block #87,409,999
29 transactions · 28 stateful · 2026-07-13 04:09:03 UTC
Parallelism
72/100
Blocked
32%
Avg conflicts / tx
0.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,409,999 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w311w416w118w523w626w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c1e34a2…a218
0x34b655…2a6f
12 touches
15 conflicts
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0x88adad52…54b7
0x34b655…2a6f
8 touches
6 conflicts
0xc335872c…4214
0x34b655…2a6f
8 touches
6 conflicts
0xaba6578d…bd48
0x34b655…2a6f
6 touches
3 conflicts
0x169daa40…3f75
0x34b655…2a6f
6 touches
3 conflicts
0xe8706f47…bacf
0x34b655…2a6f
6 touches
3 conflicts
0x94e0f6b9…3c85
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
15 conflicts on slot 0x9c1e34a23f…90a218
Audit this contract →
← previous block·next block →recent activity