← previous blocknext block →recent activity
Analyzing
Block #88,358,698
42 transactions · 38 stateful · 2026-07-17 13:56:07 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.81
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #88,358,698 · 42 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
1w02w13w26w27w38w010w011w112w013w114w015w116w217w018w021w322w423w128w529w632w933w1038w1339w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x03cf7ec2…ef5a
0x34b655…2a6f
10 touches
10 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
8 touches
6 conflicts
0x26aba004…ada0
0x34b655…2a6f
8 touches
6 conflicts
0x4560e5a8…b741
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e17e82a…9748
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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity