← previous blocknext block →recent activity

Analyzing

Block #92,063,971

21 transactions · 18 stateful · 2026-08-01 00:52:39 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,063,971  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x177211e2…1c2d

0x754704…b603

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xf152ab6e…191f

0x7b9256…1fb2

10 touches
10 conflicts

0xf152ab6e…191e

0x7b9256…1fb2

10 touches
10 conflicts

0xc6d66e7c…2bb9

0x7b9256…1fb2

10 touches
10 conflicts

0xc6d66e7c…2bb8

0x7b9256…1fb2

10 touches
10 conflicts

0xf152ab6e…1922

0x7b9256…1fb2

10 touches
10 conflicts

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)

10 conflicts on slot 0xe1f61186c5…67e2f8

← previous block·next block →recent activity