← previous blocknext block →recent activity
Analyzing
Block #87,304,079
13 transactions · 12 stateful · 2026-07-12 16:20:40 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,304,079 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w310w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xe85e763f…3b25
0x34b655…2a6f
6 touches
3 conflicts
0x22fc9794…6e93
0x34b655…2a6f
4 touches
1 conflict
0x41e3864c…5b8f
0x34b655…2a6f
4 touches
1 conflict
0x426e1f22…5ff9
0x34b655…2a6f
4 touches
1 conflict
0x5b8a1a43…4aea
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity