← previous blocknext block →recent activity
Analyzing
Block #88,356,726
20 transactions · 18 stateful · 2026-07-17 13:42:53 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,356,726 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w08w110w111w013w115w217w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbcdee322…f454
0xa6afd3…d132
4 touches
1 conflict
0x47bf4f8d…97ba
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x006ee1d9…5485
0xa6afd3…d132
4 touches
1 conflict
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x0eb5755c…51a2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity