← previous blocknext block →recent activity
Analyzing
Block #87,576,656
19 transactions · 17 stateful · 2026-07-13 22:44:21 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,576,656 · 19 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
3w04w16w07w28w39w010w111w212w315w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0xda12e7f3…e890
0x34b655…2a6f
8 touches
6 conflicts
0x925c118c…a1d8
0x34b655…2a6f
6 touches
3 conflicts
0xa055d2b9…fbb6
0x34b655…2a6f
6 touches
3 conflicts
0x347796c5…bfc0
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xff1c6931…7633
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity