← previous blocknext block →recent activity

Analyzing

Block #92,769,526

16 transactions · 14 stateful · 2026-08-03 12:02:21 UTC

Parallelism

88/100

Blocked

21%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,769,526  ·  16 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

0xaad1c5c0…ab91

0x754704…b603

4 touches
1 conflict

0xdc255d21…c377

0x754704…b603

4 touches
1 conflict

0xe20cfb89…cd07

0x754704…b603

4 touches
1 conflict

0x38d457bd…e2c1

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x8f63f383…6eda

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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 0xaad1c5c0ee…1fab91

← previous block·next block →recent activity