← previous blocknext block →recent activity
Analyzing
Block #87,063,716
19 transactions · 18 stateful · 2026-07-11 13:33:19 UTC
Parallelism
47/100
Blocked
61%
Avg conflicts / tx
1.58
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,063,716 · 19 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w613w114w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa94f6641…e11c
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
6 touches
3 conflicts
0xb35e663e…354e
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 0xa94f664112…9fe11c
Audit this contract →
← previous block·next block →recent activity