← previous blocknext block →recent activity
Analyzing
Block #87,794,366
20 transactions · 19 stateful · 2026-07-14 23:00:34 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,794,366 · 20 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
6w08w112w214w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0363d65e…06d2
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x60c4435a…22ca
0x34b655…2a6f
4 touches
1 conflict
0x6db9b542…245c
0x34b655…2a6f
4 touches
1 conflict
0x7584bc06…3463
0x34b655…2a6f
4 touches
1 conflict
0x77fb04fd…9db8
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 0x0363d65e7f…9306d2
Audit this contract →
← previous block·next block →recent activity