← previous blocknext block →recent activity
Analyzing
Block #87,317,164
18 transactions · 18 stateful · 2026-07-12 17:48:10 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,317,164 · 18 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
2w03w14w25w36w49w010w111w212w314w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e5e0c2…6e04
0x34b655…2a6f
10 touches
10 conflicts
0xb835d684…089c
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0xe3ce81c6…d48d
0x34b655…2a6f
8 touches
6 conflicts
0x7ea6a117…f2f2
0x34b655…2a6f
8 touches
6 conflicts
0x5e6ccf1a…4462
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xa4e5e0c2c4…d76e04
Audit this contract →
← previous block·next block →recent activity