← previous blocknext block →recent activity

Analyzing

Block #92,471,684

19 transactions · 19 stateful · 2026-08-02 11:03:09 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,471,684  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6b267bdf…b173

0x34b655…2a6f

4 touches
1 conflict

0x6fbc2e5a…e69c

0x34b655…2a6f

4 touches
1 conflict

0x0359c13d…9da4

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)

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity