← previous blocknext block →recent activity
Analyzing
Block #87,506,571
19 transactions · 17 stateful · 2026-07-13 14:54:53 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,506,571 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w17w28w39w410w411w514w617w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbedfd60…0fec
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfb9f51f4…0f16
0x34b655…2a6f
8 touches
6 conflicts
0x64aed863…94cd
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xfbe29649…e573
0x34b655…2a6f
6 touches
3 conflicts
0x18ca6535…87c1
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 0xbbedfd6094…580fec
Audit this contract →
← previous block·next block →recent activity