← previous blocknext block →recent activity
Analyzing
Block #87,722,825
23 transactions · 20 stateful · 2026-07-14 15:01:58 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,722,825 · 23 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
4w05w17w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
4 touches
1 conflict
0xdbc62196…3245
0x34b655…2a6f
4 touches
1 conflict
0xeeaba9d3…b491
0x34b655…2a6f
4 touches
1 conflict
0xf3e0b949…771f
0x34b655…2a6f
4 touches
1 conflict
0x072137cd…a3b8
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
0x34b655…2a6f
4 touches
1 conflict
0x427f51fd…bd80
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity