← previous blocknext block →recent activity
Analyzing
Block #99,243,471
38 transactions · 32 stateful · 2026-08-26 05:18:18 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
1.11
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,243,471 · 38 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w26w07w19w210w311w212w013w114w416w120w323w524w629w332w135w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x9ab2f865…d113
0x34b655…2a6f
8 touches
6 conflicts
0x7ea1cfdf…81c0
0xa6afd3…d132
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x94710b77…a921
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity