← previous blocknext block →recent activity
Analyzing
Block #98,989,024
124 transactions · 64 stateful · 2026-08-25 07:51:25 UTC
Parallelism
86/100
Blocked
75%
Avg conflicts / tx
2.27
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,989,024 · 124 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
1w06w07w110w012w014w115w216w320w435w537w646w748w149w251w352w454w557w758w862w966w1079w184w1186w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
34 touches
136 conflicts
0x889d5e90…929a
0x2a68ba…90c5
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x5778d110…d2e6
0xc8689a…ee79
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x38963aeb…c33f
0xa6afd3…d132
16 touches
28 conflicts
0x00000000…0002
0xbb3f3c…e046
16 touches
28 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
136 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity