← previous blocknext block →recent activity

Analyzing

Block #92,688,685

21 transactions · 18 stateful · 2026-08-03 05:15:25 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1.24

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #92,688,685  ·  21 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

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0x1bf83374…df33

0x34b655…2a6f

4 touches
1 conflict

0x56153262…21ce

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x771536e7…9794

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

15 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity