← previous blocknext block →recent activity
Analyzing
Block #88,355,638
31 transactions · 29 stateful · 2026-07-17 13:35:23 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.42
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #88,355,638 · 31 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
2w03w14w05w16w07w18w29w311w312w413w514w215w116w619w224w625w726w827w928w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf565ea1f…4245
0x34b655…2a6f
8 touches
6 conflicts
0x0e525f1d…dfed
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x876712ff…b058
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x756913cf…e7bd
0xa6afd3…d132
6 touches
3 conflicts
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
10 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity