← previous blocknext block →recent activity

Analyzing

Block #92,444,212

7 transactions · 6 stateful · 2026-08-02 08:44:57 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,444,212  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x02d79f72…b18e

0x34b655…2a6f

6 touches
3 conflicts

0x6f900be0…cd6e

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd58474a3…aff4

0x34b655…2a6f

4 touches
1 conflict

0x0835f2d8…e06a

0x34b655…2a6f

4 touches
1 conflict

0x427d1120…4eb1

0x34b655…2a6f

4 touches
1 conflict

0x43e15ca4…039d

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eeb

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

3 conflicts on slot 0x02d79f7285…53b18e

← previous block·next block →recent activity