← previous blocknext block →recent activity
Analyzing
Block #87,919,287
23 transactions · 19 stateful · 2026-07-15 12:56:05 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,919,287 · 23 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
4w09w010w111w212w313w017w118w221w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe613a978…22a4
0x34b655…2a6f
6 touches
3 conflicts
0x28c714d9…9438
0xa6afd3…d132
6 touches
3 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity