← previous blocknext block →recent activity

Analyzing

Block #94,970,216

33 transactions · 32 stateful · 2026-08-11 04:49:10 UTC

Parallelism

67/100

Blocked

63%

Avg conflicts / tx

1.76

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #94,970,216  ·  33 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

12 touches
15 conflicts

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

10 touches
10 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

10 touches
10 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

8 touches
6 conflicts

0x11b69a7e…334e

0x01bff4…1071

6 touches
3 conflicts

0x216ffe66…1f94

0x34b655…2a6f

6 touches
3 conflicts

0xa2478c84…6956

0x754704…b603

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

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity