← previous blocknext block →recent activity
Analyzing
Block #87,286,479
15 transactions · 14 stateful · 2026-07-12 14:23:00 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,286,479 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w110w213w014w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34bcdc05…6689
0x34b655…2a6f
6 touches
3 conflicts
0xddaf39ca…9bd5
0x34b655…2a6f
6 touches
3 conflicts
0xccdc32f8…72be
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x34bcdc05ee…2c6689
Audit this contract →
← previous block·next block →recent activity