← previous blocknext block →recent activity
Analyzing
Block #98,930,096
33 transactions · 32 stateful · 2026-08-25 02:54:56 UTC
Parallelism
51/100
Blocked
59%
Avg conflicts / tx
3.82
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,930,096 · 33 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
1w06w011w012w113w214w315w416w517w618w719w820w921w1022w1123w1224w1325w1426w1530w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef234cb9…7713
0x34b655…2a6f
32 touches
120 conflicts
0xac2a0273…721b
0x34b655…2a6f
32 touches
120 conflicts
0x94789504…4524
0x34b655…2a6f
32 touches
120 conflicts
0x737acb78…fce8
0x34b655…2a6f
32 touches
120 conflicts
0x222e523b…bda2
0x34b655…2a6f
26 touches
78 conflicts
0xabdf81c9…b3b0
0x34b655…2a6f
8 touches
6 conflicts
0x20b718b1…295a
0x34b655…2a6f
7 touches
6 conflicts
0xd98b3c10…67b8
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
120 conflicts on slot 0xef234cb9e5…6a7713
Audit this contract →
← previous block·next block →recent activity