← previous blocknext block →recent activity
Analyzing
Block #87,733,522
41 transactions · 36 stateful · 2026-07-14 16:13:33 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
2.73
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,733,522 · 41 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
2w03w14w05w17w013w014w115w216w317w418w519w620w721w822w923w1024w1125w626w727w832w1237w1238w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x310afe2c…83e1
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
8 touches
6 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0x8db5666d…76f0
0x34b655…2a6f
8 touches
6 conflicts
0x954b79eb…7077
0x34b655…2a6f
8 touches
6 conflicts
0x4acbdbcf…a8c6
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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity