← previous blocknext block →recent activity

Analyzing

Block #94,998,180

24 transactions · 20 stateful · 2026-08-11 07:09:48 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,998,180  ·  24 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

0x11b69a7e…334e

0x01bff4…1071

12 touches
15 conflicts

0xf7640726…19a2

0x2a68ba…90c5

10 touches
10 conflicts

0x88972961…c90c

0x851145…3f07

9 touches
10 conflicts

0x758f26d7…858f

0x01bff4…1071

4 touches
1 conflict

0xa8e98b9f…5935

0x01bff4…1071

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x889d5e90…929a

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