← previous blocknext block →recent activity
Analyzing
Block #98,837,559
29 transactions · 26 stateful · 2026-08-24 19:09:24 UTC
Parallelism
86/100
Blocked
50%
Avg conflicts / tx
0.66
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,837,559 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w18w211w012w114w117w218w321w322w223w324w327w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x41be9e75…9773
0x34b655…2a6f
6 touches
3 conflicts
0xd04c773f…7cd2
0x34b655…2a6f
6 touches
3 conflicts
0xc1a7d71a…751b
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x0f94ee4c…189a
0x1b6862…e19c
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity