← previous blocknext block →recent activity

Analyzing

Block #92,754,896

14 transactions · 13 stateful · 2026-08-03 10:48:43 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,754,896  ·  14 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

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x0d2de0f6…e6c6

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x32e2bb09…8b3a

0x34b655…2a6f

4 touches
1 conflict

0x94aff148…b584

0x34b655…2a6f

4 touches
1 conflict

0xca116de3…3352

0x34b655…2a6f

4 touches
1 conflict

0x9fd37234…2731

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0x737acb7813…fafce8

← previous block·next block →recent activity