← previous blocknext block →recent activity
Analyzing
Block #98,605,067
35 transactions · 35 stateful · 2026-08-23 23:23:11 UTC
Parallelism
66/100
Blocked
63%
Avg conflicts / tx
2.03
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #98,605,067 · 35 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w07w08w09w010w111w212w313w415w216w318w119w421w722w824w225w126w132w933w1034w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xfc81faf7…1417
0x34b655…2a6f
10 touches
10 conflicts
0x627738d1…db02
0x34b655…2a6f
10 touches
10 conflicts
0xe62e1553…ed4b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity