← previous blocknext block →recent activity
Analyzing
Block #87,739,088
18 transactions · 16 stateful · 2026-07-14 16:50:46 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,739,088 · 18 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
1w02w13w26w07w18w210w011w112w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22fc9794…6e93
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x49a97bff…33ed
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x80fd3987…2314
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 0x22fc9794dc…d16e93
Audit this contract →
← previous block·next block →recent activity