← previous blocknext block →recent activity
Analyzing
Block #88,353,212
15 transactions · 13 stateful · 2026-07-17 13:18:58 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,353,212 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w39w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x62b86e44…980e
0x851145…3f07
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x458b9085…9ee2
0x34b655…2a6f
4 touches
1 conflict
0x73d70be1…c3d1
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity