← previous blocknext block →recent activity

Analyzing

Block #92,761,395

21 transactions · 19 stateful · 2026-08-03 11:21:25 UTC

Parallelism

52/100

Blocked

63%

Avg conflicts / tx

1.33

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #92,761,395  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x67b8a942…7882

0x34b655…2a6f

6 touches
3 conflicts

0x21605a79…d719

0x34b655…2a6f

6 touches
3 conflicts

0x94aff148…b584

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

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

10 conflicts on slot 0x737acb7813…fafce8

← previous block·next block →recent activity