← previous blocknext block →recent activity
Analyzing
Block #98,766,769
59 transactions · 52 stateful · 2026-08-24 13:13:02 UTC
Parallelism
92/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,766,769 · 59 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
5w011w112w216w317w419w020w153w054w155w056w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4a65c5c3…6a0d
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x5a6c91e3…7d42
0x34b655…2a6f
4 touches
1 conflict
0x6bb40b23…f781
0x34b655…2a6f
4 touches
1 conflict
0x9daee8ff…6f86
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity