← previous blocknext block →recent activity
Analyzing
Block #87,513,133
17 transactions · 16 stateful · 2026-07-13 15:38:48 UTC
Parallelism
53/100
Blocked
63%
Avg conflicts / tx
1.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,513,133 · 17 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
1w02w13w24w35w06w410w511w612w714w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cf1f868…c5af
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x2f702750…347d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x157dbfb2…4089
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 0x8cf1f86890…38c5af
Audit this contract →
← previous block·next block →recent activity