← previous blocknext block →recent activity

Analyzing

Block #92,813,210

25 transactions · 22 stateful · 2026-08-03 15:42:09 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,813,210  ·  25 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x0a6f5e37…6c3c

0x34b655…2a6f

4 touches
1 conflict

0x1526b11f…8b21

0x34b655…2a6f

4 touches
1 conflict

0x45cd503b…4d50

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x7be3246e…f89f

0x34b655…2a6f

4 touches
1 conflict

0x856d2776…04c9

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

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

← previous block·next block →recent activity