← previous blocknext block →recent activity
Analyzing
Block #99,668,535
37 transactions · 37 stateful · 2026-08-27 17:05:18 UTC
Parallelism
57/100
Blocked
68%
Avg conflicts / tx
2.41
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #99,668,535 · 37 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w310w111w013w215w317w319w521w223w625w128w733w1234w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
8 touches
6 conflicts
0xb64b9585…6270
0x34b655…2a6f
8 touches
6 conflicts
0x0a6cb118…4ca7
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0db07ef0…b141
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity