← previous blocknext block →recent activity

Analyzing

Block #94,486,913

18 transactions · 17 stateful · 2026-08-09 12:16:47 UTC

Parallelism

89/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #94,486,913  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe97ff784…ae17

0x34b655…2a6f

4 touches
1 conflict

0xfafd095f…5d95

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x7239a7a0…e541

0x34b655…2a6f

4 touches
1 conflict

0x7485f8af…7362

0x34b655…2a6f

4 touches
1 conflict

0x74f95963…01a2

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)

1 conflict on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity