← previous blocknext block →recent activity

Analyzing

Block #92,448,912

24 transactions · 22 stateful · 2026-08-02 09:08:35 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,448,912  ·  24 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

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x31b39922…1e65

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x4fb86cd0…c67b

0x34b655…2a6f

4 touches
1 conflict

0x4fb86cd0…c67c

0x34b655…2a6f

4 touches
1 conflict

0x5649379f…d9eb

0x34b655…2a6f

4 touches
1 conflict

0x79ace5b6…8d37

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 0x92385428ad…dc6941

← previous block·next block →recent activity