← previous blocknext block →recent activity

Analyzing

Block #92,761,646

25 transactions · 24 stateful · 2026-08-03 11:22:41 UTC

Parallelism

52/100

Blocked

63%

Avg conflicts / tx

1.72

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #92,761,646  ·  25 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xbcbf5d09…8bac

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0x8e28932e…605f

0x34b655…2a6f

8 touches
8 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

8 touches
6 conflicts

0x948836ff…59ab

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity