← previous blocknext block →recent activity
Analyzing
Block #87,707,549
30 transactions · 24 stateful · 2026-07-14 13:19:37 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,707,549 · 30 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
1w02w13w29w010w112w015w016w317w118w220w322w227w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc1bcd919…07fe
0xd32edf…ff58
7 touches
6 conflicts
0xa1f1e8db…337a
0x34b655…2a6f
6 touches
3 conflicts
0x95144060…078d
0x34b655…2a6f
6 touches
3 conflicts
0x86780cc1…e5e2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x4940bb84…4ec2
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity