← previous blocknext block →recent activity

Analyzing

Block #92,310,923

14 transactions · 11 stateful · 2026-08-01 21:34:40 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,310,923  ·  14 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

0x177211e2…1c2d

0x754704…b603

4 touches
1 conflict

0xe1f61186…e2f8

0x754704…b603

4 touches
1 conflict

0x00000000…0006

0x7b9256…1fb2

4 touches
1 conflict

0x7c024f45…b100

0x7b9256…1fb2

4 touches
1 conflict

0x7c024f45…b101

0x7b9256…1fb2

4 touches
1 conflict

0x836c0fe2…48a9

0x7b9256…1fb2

4 touches
1 conflict

0x836c0fe2…48aa

0x7b9256…1fb2

4 touches
1 conflict

0x836c0fe2…48ad

0x7b9256…1fb2

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 0x177211e248…161c2d

← previous block·next block →recent activity