← previous blocknext block →recent activity
Analyzing
Block #99,290,741
31 transactions · 24 stateful · 2026-08-26 09:16:10 UTC
Parallelism
81/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,290,741 · 31 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
1w05w07w08w19w210w115w116w219w320w321w422w523w424w429w230w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae62d2a9…84dd
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xb5924647…4cf1
0x34b655…2a6f
6 touches
3 conflicts
0xb9868b52…c77f
0x34b655…2a6f
6 touches
3 conflicts
0xc53799eb…d928
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
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
10 conflicts on slot 0xae62d2a96c…2284dd
Audit this contract →
← previous block·next block →recent activity