← previous blocknext block →recent activity
Analyzing
Block #87,621,719
18 transactions · 17 stateful · 2026-07-14 03:45:42 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,621,719 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w510w011w112w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f4727d…cdb7
0x34b655…2a6f
14 touches
21 conflicts
0xcd26ecec…e406
0x34b655…2a6f
12 touches
15 conflicts
0x49f75237…44f4
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0xf4d0bddb…07a4
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x34d95d94…3a16
0x34b655…2a6f
12 touches
15 conflicts
0x875164c2…f8a2
0x34b655…2a6f
12 touches
15 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
21 conflicts on slot 0xf2f4727df6…a5cdb7
Audit this contract →
← previous block·next block →recent activity