← previous blocknext block →recent activity

Analyzing

Block #95,024,288

17 transactions · 17 stateful · 2026-08-11 09:21:10 UTC

Parallelism

59/100

Blocked

47%

Avg conflicts / tx

1.41

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,024,288  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xa1087a5c…66c4

0x754704…b603

14 touches
21 conflicts

0x8a9969f9…3a1c

0x065c9d…c394

6 touches
3 conflicts

0x11258774…9892

0x2a68ba…90c5

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xb1add938…57f7

0x40c49f…2af0

4 touches
1 conflict

0x3a921be0…779c

0x2a68ba…90c5

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: USDC (USDC)

21 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity