← previous blocknext block →recent activity
Analyzing
Block #98,748,122
77 transactions · 59 stateful · 2026-08-24 11:39:05 UTC
Parallelism
75/100
Blocked
66%
Avg conflicts / tx
2.12
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #98,748,122 · 77 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w07w18w19w110w213w014w115w216w333w434w535w638w739w840w941w1042w1147w260w368w275w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x6d8ad688…4bf5
0xa6afd3…d132
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x5b09bf44…5907
0xa6afd3…d132
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity