← previous blocknext block →recent activity
Analyzing
Block #99,353,255
38 transactions · 36 stateful · 2026-08-26 14:30:40 UTC
Parallelism
55/100
Blocked
72%
Avg conflicts / tx
3.24
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #99,353,255 · 38 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w310w411w512w613w714w815w916w218w422w523w629w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xd689a6a5…0d01
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
8 touches
6 conflicts
0x17ff2059…ddb4
0x34b655…2a6f
6 touches
3 conflicts
0x364d1d02…0528
0x34b655…2a6f
6 touches
3 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
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
45 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity