← previous blocknext block →recent activity
Analyzing
Block #98,380,749
14 transactions · 13 stateful · 2026-08-23 04:14:35 UTC
Parallelism
50/100
Blocked
62%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,380,749 · 14 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
1w02w13w24w37w48w59w110w011w113w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb7b16dd0…0426
0x34b655…2a6f
6 touches
3 conflicts
0x2da3949a…1d44
0x34b655…2a6f
4 touches
1 conflict
0x3f5831e5…02b2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x711ceb8d…5202
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity