← previous blocknext block →recent activity

Analyzing

Block #92,600,977

24 transactions · 21 stateful · 2026-08-02 21:53:25 UTC

Parallelism

71/100

Blocked

48%

Avg conflicts / tx

1.08

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,600,977  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0x0672e4a2…8d1f

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
4 conflicts

0x8cd684d0…c3cb

0x34b655…2a6f

6 touches
3 conflicts

0x4561c02e…963c

0xd32edf…ff58

5 touches
3 conflicts

0xc0f29314…17fd

0x1b6862…e19c

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity