← previous blocknext block →recent activity
Analyzing
Block #87,504,009
19 transactions · 16 stateful · 2026-07-13 14:37:42 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,504,009 · 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
1w02w13w09w010w111w212w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x169daa40…3f75
0x34b655…2a6f
6 touches
3 conflicts
0x2089dcc1…8f89
0x34b655…2a6f
6 touches
3 conflicts
0x0adf48a7…c84a
0x34b655…2a6f
6 touches
3 conflicts
0x02001509…ba7d
0x0a2fbf…29b1
4 touches
1 conflict
0x10168934…234b
0x0a2fbf…29b1
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x3f93d576…f1de
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 0x169daa4085…fe3f75
Audit this contract →
← previous block·next block →recent activity