← previous blocknext block →recent activity
Analyzing
Block #87,313,538
19 transactions · 18 stateful · 2026-07-12 17:23:54 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,313,538 · 19 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
1w02w14w05w16w27w38w49w511w413w514w115w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0xa013ecc1…7c8f
0x34b655…2a6f
8 touches
6 conflicts
0x72880226…1435
0x34b655…2a6f
6 touches
3 conflicts
0x033dddd2…ac15
0x34b655…2a6f
6 touches
3 conflicts
0xdb564c7f…72f9
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0f6666e6…f280
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity