← previous blocknext block →recent activity
Analyzing
Block #99,359,751
24 transactions · 22 stateful · 2026-08-26 15:03:28 UTC
Parallelism
75/100
Blocked
55%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,359,751 · 24 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
1w02w15w26w27w18w29w011w012w316w117w118w221w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x71717491…10cf
0xa6afd3…d132
6 touches
3 conflicts
0x1d10f24a…2fb8
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
6 touches
3 conflicts
0x10d80fee…dbda
0x2b46c0…1669
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity