← previous blocknext block →recent activity
Analyzing
Block #98,505,224
100 transactions · 70 stateful · 2026-08-23 14:42:20 UTC
Parallelism
78/100
Blocked
79%
Avg conflicts / tx
3.51
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #98,505,224 · 100 txs across 22 waves · depth 22
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w211w212w322w426w556w1058w1161w1265w13
- 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
24 touches
66 conflicts
0x90b27515…bfdb
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…001d
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…002d
0x1b6862…e19c
22 touches
55 conflicts
0x3293a887…4402
0x1b6862…e19c
22 touches
55 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
22 touches
55 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
22 touches
55 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