← previous blocknext block →recent activity
Analyzing
Block #98,424,083
30 transactions · 26 stateful · 2026-08-23 07:52:37 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,424,083 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w08w19w210w011w113w214w316w017w118w219w320w421w124w525w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd33c2ab5…ccc3
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xcdd556aa…31d0
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x8259a03c…382d
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
10 conflicts on slot 0xd33c2ab533…e1ccc3
Audit this contract →
← previous block·next block →recent activity