← previous blocknext block →recent activity

Analyzing

Block #94,834,347

21 transactions · 21 stateful · 2026-08-10 17:25:48 UTC

Parallelism

86/100

Blocked

24%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,834,347  ·  21 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

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x2b5101ac…090b

0x34b655…2a6f

4 touches
1 conflict

0x42e5184f…4e8b

0x34b655…2a6f

4 touches
1 conflict

0x48203298…65cb

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5f7b9c22…6abb

0x34b655…2a6f

4 touches
1 conflict

0xbceecf11…0120

0x34b655…2a6f

4 touches
1 conflict

0x00000000…00c9

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 0xbde524f475…b143bf

← previous block·next block →recent activity