← previous blocknext block →recent activity
Analyzing
Block #98,647,577
19 transactions · 17 stateful · 2026-08-24 03:04:15 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,647,577 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w08w09w111w212w313w214w317w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1408e7c7…f324
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x58c1562d…8d82
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x705a9a1a…db08
0x34b655…2a6f
4 touches
1 conflict
0x77100a2a…91a4
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
6 conflicts on slot 0x1408e7c773…87f324
Audit this contract →
← previous block·next block →recent activity