← previous blocknext block →recent activity
Analyzing
Block #98,207,832
25 transactions · 24 stateful · 2026-08-22 13:44:38 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,207,832 · 25 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
3w04w06w07w18w211w112w013w114w216w218w319w320w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb77dc863…dd3d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x68106229…7057
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xa877e7ca…2315
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x0080d53f…5175
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 0xb77dc86363…59dd3d
Audit this contract →
← previous block·next block →recent activity