← previous blocknext block →recent activity
Analyzing
Block #87,711,043
79 transactions · 57 stateful · 2026-07-14 13:43:00 UTC
Parallelism
77/100
Blocked
79%
Avg conflicts / tx
2.91
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,711,043 · 79 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
1w02w13w24w05w16w07w19w011w112w317w418w528w429w530w631w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
34 touches
136 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
16 touches
28 conflicts
0x0f8965bb…e238
0x34b655…2a6f
14 touches
21 conflicts
0xee75c266…f8c6
0x34b655…2a6f
14 touches
21 conflicts
0x181ad9cf…26f4
0x34b655…2a6f
14 touches
21 conflicts
0x2754c3f9…9863
0x34b655…2a6f
14 touches
21 conflicts
0x880fc665…31e3
0x34b655…2a6f
14 touches
21 conflicts
0x9ad325f5…cc43
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
136 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity