← previous blocknext block →recent activity

Analyzing

Block #92,060,778

14 transactions · 13 stateful · 2026-08-01 00:36:36 UTC

Parallelism

86/100

Blocked

15%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,060,778  ·  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

0xe1f61186…e2f8

0x754704…b603

4 touches
1 conflict

0x00000000…0006

0x7b9256…1fb2

4 touches
1 conflict

0x3be65138…ea20

0x7b9256…1fb2

4 touches
1 conflict

0x3be65138…ea21

0x7b9256…1fb2

4 touches
1 conflict

0x992fec48…e0c6

0x7b9256…1fb2

4 touches
1 conflict

0x992fec48…e0c7

0x7b9256…1fb2

4 touches
1 conflict

0x992fec48…e0ca

0x7b9256…1fb2

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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 0xe1f61186c5…67e2f8

← previous block·next block →recent activity