← previous blocknext block →recent activity

Analyzing

Block #92,525,364

19 transactions · 18 stateful · 2026-08-02 15:33:08 UTC

Parallelism

63/100

Blocked

56%

Avg conflicts / tx

1.79

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,525,364  ·  19 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

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0xa0d3a786…91d9

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002d

0x1b6862…e19c

8 touches
6 conflicts

0xb538c6fa…9aea

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity