← previous blocknext block →recent activity
Analyzing
Block #98,566,274
21 transactions · 21 stateful · 2026-08-23 20:01:00 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,566,274 · 21 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
1w05w06w110w111w212w313w314w415w517w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x161014f7…6f03
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0x523de645…4f58
0x34b655…2a6f
6 touches
3 conflicts
0x998a1167…81f9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 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: Perpl
3 conflicts on slot 0x161014f761…f26f03
Audit this contract →
← previous block·next block →recent activity