← previous blocknext block →recent activity

Analyzing

Block #93,490,389

16 transactions · 14 stateful · 2026-08-06 00:29:16 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,490,389  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x10797f0b…439a

0x34b655…2a6f

4 touches
1 conflict

0x1caf0c05…15ce

0x34b655…2a6f

4 touches
1 conflict

0x4175950a…1dfe

0x34b655…2a6f

4 touches
1 conflict

0x6f97afda…faec

0x34b655…2a6f

4 touches
1 conflict

0xa86351b8…2c5a

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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