← previous blocknext block →recent activity

Analyzing

Block #92,462,525

19 transactions · 18 stateful · 2026-08-02 10:17:03 UTC

Parallelism

58/100

Blocked

61%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #92,462,525  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0xaf151f7f…3fe4

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0xcad937e9…7870

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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

6 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity