← previous blocknext block →recent activity
Analyzing
Block #87,725,905
19 transactions · 17 stateful · 2026-07-14 15:22:34 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
1.26
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,725,905 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w29w310w411w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x15c7c8c1…a083
0xd32edf…ff58
9 touches
10 conflicts
0x5ec64628…72e4
0x34b655…2a6f
6 touches
3 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x559bc887…2da8
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0xad0c7701…1d83
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity