← previous blocknext block →recent activity
Analyzing
Block #87,911,683
13 transactions · 13 stateful · 2026-07-15 12:05:15 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,911,683 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w28w39w410w112w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6666e6…f280
0x34b655…2a6f
8 touches
6 conflicts
0xa013ecc1…7c8f
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0xa0a5bed4…1d15
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 0x0f6666e640…06f280
Audit this contract →
← previous block·next block →recent activity