← previous blocknext block →recent activity
Analyzing
Block #87,683,068
26 transactions · 25 stateful · 2026-07-14 10:35:42 UTC
Parallelism
58/100
Blocked
48%
Avg conflicts / tx
1.5
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,683,068 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w615w516w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x08330b36…ae29
0x34b655…2a6f
8 touches
6 conflicts
0x864353d4…dcb7
0x34b655…2a6f
8 touches
6 conflicts
0x2fdfa032…139c
0x34b655…2a6f
6 touches
3 conflicts
0x308ebcfd…135b
0x34b655…2a6f
6 touches
3 conflicts
0x34786594…61d6
0x34b655…2a6f
6 touches
3 conflicts
0x3a20350d…e8e6
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity