← previous blocknext block →recent activity

Analyzing

Block #92,765,492

25 transactions · 23 stateful · 2026-08-03 11:42:04 UTC

Parallelism

80/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,765,492  ·  25 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x9365e097…ff56

0x34b655…2a6f

4 touches
1 conflict

0xca2926e0…61b5

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xf15273a1…2c52

0x34b655…2a6f

4 touches
1 conflict

0xfb4cb196…8c4a

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 0xc824469a90…af6425

← previous block·next block →recent activity