← previous blocknext block →recent activity
Analyzing
Block #99,448,254
38 transactions · 37 stateful · 2026-08-26 22:29:11 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
1.87
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #99,448,254 · 38 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w06w07w110w011w112w213w014w316w318w419w321w223w426w129w531w733w935w1136w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0x0f517bce…6081
0xd32edf…ff58
9 touches
10 conflicts
0xbd590df7…9891
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x2caeb7f5…b6bb
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