← previous blocknext block →recent activity
Analyzing
Block #98,676,427
14 transactions · 14 stateful · 2026-08-24 05:34:41 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,676,427 · 14 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
1w02w13w04w16w07w29w310w413w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27b6010e…e4aa
0x34b655…2a6f
8 touches
6 conflicts
0x40850b96…65bb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
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 0x27b6010e94…34e4aa
Audit this contract →
← previous block·next block →recent activity