← previous blocknext block →recent activity
Analyzing
Block #98,767,928
30 transactions · 27 stateful · 2026-08-24 13:18:52 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
1.1
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #98,767,928 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w48w09w010w111w212w313w417w521w122w124w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
10 touches
10 conflicts
0xfa7e4305…0732
0xd32edf…ff58
9 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2431d060…6a71
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity