← previous blocknext block →recent activity
Analyzing
Block #87,718,301
24 transactions · 24 stateful · 2026-07-14 14:31:44 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,718,301 · 24 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
2w03w16w17w28w39w412w415w517w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f5b72a…22e0
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x5b33f5b9…4bab
0x34b655…2a6f
6 touches
3 conflicts
0x689841cb…6392
0x34b655…2a6f
6 touches
3 conflicts
0x7525206c…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x807bf45f…5016
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
6 conflicts on slot 0x22f5b72adb…1822e0
Audit this contract →
← previous block·next block →recent activity