← previous blocknext block →recent activity

Analyzing

Block #90,817,143

11 transactions · 10 stateful · 2026-07-27 16:17:07 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,817,143  ·  11 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

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641d

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…642d

0x34b655…2a6f

4 touches
1 conflict

0xfcfb570f…cf1c

0x34b655…2a6f

4 touches
1 conflict

0x11b69a7e…334e

0x01bff4…1071

4 touches
1 conflict

0x00000000…00c9

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