← previous blocknext block →recent activity
Analyzing
Block #99,449,566
44 transactions · 42 stateful · 2026-08-26 22:35:47 UTC
Parallelism
61/100
Blocked
71%
Avg conflicts / tx
2.91
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #99,449,566 · 44 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
1w02w13w24w05w06w17w29w210w311w420w321w222w624w125w726w828w932w336w940w1341w1442w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x51af0e92…4020
0x34b655…2a6f
10 touches
10 conflicts
0xcf11cf1a…ec04
0x34b655…2a6f
10 touches
10 conflicts
0xf34802b3…9f14
0x1b6862…e19c
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity