← previous blocknext block →recent activity
Analyzing
Block #88,356,084
22 transactions · 19 stateful · 2026-07-17 13:38:29 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,356,084 · 22 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
2w03w14w25w07w08w110w013w014w115w216w017w218w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a38e46…a68c
0x34b655…2a6f
6 touches
3 conflicts
0x006ee1d9…5485
0xa6afd3…d132
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xf57998a0…388f
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf7640726…19a2
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
3 conflicts on slot 0xe5a38e469a…0da68c
Audit this contract →
← previous block·next block →recent activity