← previous blocknext block →recent activity
Analyzing
Block #88,354,563
18 transactions · 13 stateful · 2026-07-17 13:28:07 UTC
Parallelism
78/100
Blocked
46%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,354,563 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w113w014w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
6 touches
3 conflicts
0x0227484c…b688
0x34b655…2a6f
4 touches
1 conflict
0x267e6f2b…14f2
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x6ca8cf24…7151
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity