← previous blocknext block →recent activity
Analyzing
Block #96,835,626
24 transactions · 22 stateful · 2026-08-17 17:27:59 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,835,626 · 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
1w03w04w15w26w07w18w19w212w016w317w118w222w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc81b430f…10a7
0x065c9d…c394
4 touches
1 conflict
0x0e0a3c1a…f9fb
0x34b655…2a6f
4 touches
1 conflict
0x334649c0…069e
0x34b655…2a6f
4 touches
1 conflict
0x3d158563…8713
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity