← previous blocknext block →recent activity
Analyzing
Block #99,819,505
29 transactions · 26 stateful · 2026-08-28 05:50:08 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,819,505 · 29 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
2w06w17w19w010w111w212w113w214w317w321w122w023w424w125w526w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0b7622d…b57e
0x34b655…2a6f
8 touches
6 conflicts
0x0d2d23d3…8a3a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xd08db6ee…a943
0x40c49f…2af0
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 0xf0b7622dee…97b57e
Audit this contract →
← previous block·next block →recent activity