← previous blocknext block →recent activity

Analyzing

Block #92,212,908

14 transactions · 14 stateful · 2026-08-01 13:21:42 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,212,908  ·  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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc0eb79d1…29a4

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x64e5f38d…187c

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b77

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x9c69390f…0832

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 0xc824469a90…af6425

← previous block·next block →recent activity