← previous blocknext block →recent activity
Analyzing
Block #88,359,138
49 transactions · 41 stateful · 2026-07-17 13:59:04 UTC
Parallelism
65/100
Blocked
66%
Avg conflicts / tx
2.18
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #88,359,138 · 49 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w210w011w112w217w018w119w220w321w422w526w627w728w829w930w131w232w1033w336w437w1038w342w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xff196840…a453
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x2f461725…5ab2
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xb9834665…e363
0x34b655…2a6f
8 touches
6 conflicts
0xd5ab2f5b…092b
0x34b655…2a6f
8 touches
6 conflicts
0x97c67486…27fe
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity