← previous blocknext block →recent activity
Analyzing
Block #99,867,017
22 transactions · 22 stateful · 2026-08-28 09:50:20 UTC
Parallelism
64/100
Blocked
59%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,867,017 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w110w211w312w413w514w615w716w218w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb856d1a1…1f18
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x2130a548…c1de
0x34b655…2a6f
8 touches
6 conflicts
0xa7867a0c…4c51
0x34b655…2a6f
8 touches
6 conflicts
0xfc5d79bb…362c
0x34b655…2a6f
8 touches
6 conflicts
0x84611dd3…b341
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0c396575…8af6
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
15 conflicts on slot 0xb856d1a127…bf1f18
Audit this contract →
← previous block·next block →recent activity