← previous blocknext block →recent activity
Analyzing
Block #87,730,242
43 transactions · 38 stateful · 2026-07-14 15:51:36 UTC
Parallelism
70/100
Blocked
61%
Avg conflicts / tx
2.35
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,730,242 · 43 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w19w011w114w115w216w317w418w519w620w729w835w237w138w241w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
16 touches
28 conflicts
0x428b6e5b…8909
0x34b655…2a6f
16 touches
28 conflicts
0x32792f31…fc3e
0x34b655…2a6f
14 touches
21 conflicts
0x727b1b1a…e403
0x34b655…2a6f
14 touches
21 conflicts
0x7a12cccc…57f8
0x34b655…2a6f
14 touches
21 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
14 touches
21 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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity