← previous blocknext block →recent activity
Analyzing
Block #87,920,386
31 transactions · 25 stateful · 2026-07-15 13:03:27 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,920,386 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w17w014w015w117w218w019w120w223w325w129w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5857a633…0d13
0xd32edf…ff58
7 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2c3159a6…a84b
0x34b655…2a6f
4 touches
1 conflict
0x3b63666d…e4f6
0x34b655…2a6f
4 touches
1 conflict
0x3b63666d…e4f7
0x34b655…2a6f
4 touches
1 conflict
0x477df9ac…189c
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity