← previous blocknext block →recent activity
Analyzing
Block #88,185,447
30 transactions · 23 stateful · 2026-07-16 18:37:05 UTC
Parallelism
63/100
Blocked
52%
Avg conflicts / tx
1.6
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #88,185,447 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w19w010w111w212w313w414w515w616w721w823w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x2f461725…5ab2
0x34b655…2a6f
8 touches
6 conflicts
0xa55c4598…2988
0x34b655…2a6f
6 touches
3 conflicts
0xc6fa5268…6ae0
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x85b992ec…db0e
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity