← previous blocknext block →recent activity
Analyzing
Block #87,614,444
17 transactions · 15 stateful · 2026-07-14 02:57:04 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,614,444 · 17 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
1w05w06w17w28w110w011w312w413w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0x0bce8fb9…edb6
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xb568bd0a…0a72
0x34b655…2a6f
6 touches
3 conflicts
0x169daa40…3f75
0x34b655…2a6f
6 touches
3 conflicts
0xbbee202a…8912
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
15 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity