← previous blocknext block →recent activity

Analyzing

Block #92,333,024

18 transactions · 15 stateful · 2026-08-01 23:25:49 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,333,024  ·  18 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x033cf007…136d

0x34b655…2a6f

6 touches
3 conflicts

0xa1e3d047…b24d

0x34b655…2a6f

6 touches
3 conflicts

0xa4e9800f…4ab1

0x34b655…2a6f

6 touches
3 conflicts

0x5e8ddd73…4dfb

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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: Perpl

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity