← previous blocknext block →recent activity
Analyzing
Block #98,748,383
112 transactions · 70 stateful · 2026-08-24 11:40:24 UTC
Parallelism
84/100
Blocked
71%
Avg conflicts / tx
1.89
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #98,748,383 · 112 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w28w010w111w014w215w316w321w022w127w028w143w345w446w547w649w751w852w997w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0x7de57974…f5ba
0x34b655…2a6f
12 touches
15 conflicts
0x597d5b5f…e0ed
0xd32edf…ff58
11 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity