← previous blocknext block →recent activity
Analyzing
Block #98,740,466
20 transactions · 17 stateful · 2026-08-24 11:00:34 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,740,466 · 20 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
4w07w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2805009c…e080
0x40c49f…2af0
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
12 touches
15 conflicts
0x515b3963…4331
0x065c9d…c394
2 touches
0 conflicts
0x55c79370…9949
0x065c9d…c394
2 touches
0 conflicts
0x8ce9d3b7…d82b
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
2 touches
0 conflicts
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: 0x40c49f17…d22af0
15 conflicts on slot 0x2805009c0c…0ce080
Audit this contract →
← previous block·next block →recent activity