← previous blocknext block →recent activity

Analyzing

Block #92,274,569

23 transactions · 19 stateful · 2026-08-01 18:31:50 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,274,569  ·  23 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

0x092832cd…7b28

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x721b4d3a…1247

0x34b655…2a6f

8 touches
6 conflicts

0x4b628349…f327

0x34b655…2a6f

4 touches
1 conflict

0x746bcce3…d0ce

0x34b655…2a6f

4 touches
1 conflict

0x7c09c53e…64b4

0x34b655…2a6f

4 touches
1 conflict

0x85eb1316…bb9e

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 0x092832cdd7…187b28

← previous block·next block →recent activity