← previous blocknext block →recent activity
Analyzing
Block #87,692,726
17 transactions · 16 stateful · 2026-07-14 11:40:15 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,692,726 · 17 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
3w07w08w19w210w311w413w516w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa27f1875…0c5d
0x34b655…2a6f
8 touches
6 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xe7aba1c7…1141
0x34b655…2a6f
6 touches
3 conflicts
0xb268a300…5f0c
0x34b655…2a6f
6 touches
3 conflicts
0x57b57f51…2449
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 0xa27f187578…2a0c5d
Audit this contract →
← previous block·next block →recent activity