← previous blocknext block →recent activity

Analyzing

Block #94,915,373

18 transactions · 18 stateful · 2026-08-11 00:13:20 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.78

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,915,373  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd30f9e74…d404

0x34b655…2a6f

6 touches
3 conflicts

0x11b69a7e…334e

0x01bff4…1071

6 touches
3 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x5d9698ff…d8f9

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity