← previous blocknext block →recent activity
Analyzing
Block #87,730,171
37 transactions · 31 stateful · 2026-07-14 15:51:07 UTC
Parallelism
51/100
Blocked
65%
Avg conflicts / tx
2.95
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,730,171 · 37 txs across 18 waves · depth 18
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
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w211w312w413w514w615w716w817w918w1019w1120w1221w1323w1426w1531w934w1635w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
14 touches
21 conflicts
0x8d59b150…7225
0x34b655…2a6f
10 touches
10 conflicts
0x98212952…9ba6
0x34b655…2a6f
10 touches
10 conflicts
0x310afe2c…83e1
0x34b655…2a6f
8 touches
6 conflicts
0xa55c4598…2988
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x856d2776…04c9
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity