← previous blocknext block →recent activity
Analyzing
Block #87,752,989
43 transactions · 37 stateful · 2026-07-14 18:23:46 UTC
Parallelism
65/100
Blocked
68%
Avg conflicts / tx
2.28
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,752,989 · 43 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w213w114w315w416w521w222w323w426w127w628w729w835w936w1038w1240w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc616f7f…6178
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xa558e115…fc88
0x34b655…2a6f
8 touches
6 conflicts
0x747f609d…1555
0x34b655…2a6f
8 touches
6 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 0xcc616f7f2b…a56178
Audit this contract →
← previous block·next block →recent activity