← previous blocknext block →recent activity
Analyzing
Block #98,203,335
29 transactions · 27 stateful · 2026-08-22 13:22:00 UTC
Parallelism
42/100
Blocked
67%
Avg conflicts / tx
3.17
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,203,335 · 29 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
1w03w04w05w17w010w111w212w313w416w517w618w721w1022w1123w1225w1426w1527w1628w1
- 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
14 touches
21 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x1fd77335…9120
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
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