← previous blocknext block →recent activity

Analyzing

Block #92,574,651

12 transactions · 12 stateful · 2026-08-02 19:41:00 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,574,651  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x2b0da3da…c9f3

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x620b761c…270e

0x34b655…2a6f

4 touches
1 conflict

0x79f335e3…93aa

0x34b655…2a6f

4 touches
1 conflict

0xa01f2285…f16f

0x34b655…2a6f

4 touches
1 conflict

0xb027a20d…5efe

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity