← previous blocknext block →recent activity
Analyzing
Block #98,740,401
24 transactions · 20 stateful · 2026-08-24 11:00:15 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,740,401 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w19w212w315w316w417w518w423w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5636ef5b…c11d
0x34b655…2a6f
10 touches
10 conflicts
0xe4af4c87…9964
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf98c943e…7c44
0x34b655…2a6f
8 touches
6 conflicts
0x998a1167…81f9
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
10 conflicts on slot 0x5636ef5bd2…49c11d
Audit this contract →
← previous block·next block →recent activity