← previous blocknext block →recent activity
Analyzing
Block #99,878,581
28 transactions · 21 stateful · 2026-08-28 10:48:34 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,878,581 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w18w09w010w111w212w113w217w019w121w222w325w027w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x580f9523…350c
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x08db2444…22b2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x70d81211…f49f
0x34b655…2a6f
4 touches
1 conflict
0x8692136a…16fc
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 0x580f952320…e4350c
Audit this contract →
← previous block·next block →recent activity