← previous blocknext block →recent activity
Analyzing
Block #88,092,431
39 transactions · 34 stateful · 2026-07-16 08:14:09 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.87
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #88,092,431 · 39 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
2w03w14w25w36w426w528w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x529e53cf…38e4
0xa6afd3…d132
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x989252a1…d812
0xa6afd3…d132
14 touches
21 conflicts
0x55012d1a…3907
0x2b46c0…1669
10 touches
10 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
10 touches
10 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity