← previous blocknext block →recent activity
Analyzing
Block #98,524,809
24 transactions · 17 stateful · 2026-08-23 16:24:44 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,524,809 · 24 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
4w05w16w07w112w013w114w215w017w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
6 touches
3 conflicts
0xf8cb14ea…b0eb
0x34b655…2a6f
6 touches
3 conflicts
0xbc308fc6…d8ea
0xd32edf…ff58
5 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x68531239…e9a3
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity