← previous blocknext block →recent activity
Analyzing
Block #98,749,082
52 transactions · 38 stateful · 2026-08-24 11:43:55 UTC
Parallelism
54/100
Blocked
76%
Avg conflicts / tx
2.67
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #98,749,082 · 52 txs across 24 waves · depth 24
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
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w510w622w323w426w737w451w23
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
20 touches
45 conflicts
0x92385428…6941
0x34b655…2a6f
18 touches
36 conflicts
0xfa0c5188…06f2
0x34b655…2a6f
16 touches
28 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xd08cca72…5ec0
0xd32edf…ff58
9 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity