← previous blocknext block →recent activity

Analyzing

Block #92,764,635

23 transactions · 21 stateful · 2026-08-03 11:37:45 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,764,635  ·  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

0x81561f70…fefd

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x430906fc…d9a4

0x34b655…2a6f

4 touches
1 conflict

0x44df3c2a…bafe

0x34b655…2a6f

4 touches
1 conflict

0x44df3c2a…baff

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…aaff

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…ab00

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 0x81561f70ba…26fefd

← previous block·next block →recent activity