← previous blocknext block →recent activity

Analyzing

Block #92,975,729

22 transactions · 20 stateful · 2026-08-04 05:19:56 UTC

Parallelism

55/100

Blocked

60%

Avg conflicts / tx

2.18

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #92,975,729  ·  22 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

18 touches
36 conflicts

0x482471ad…122f

0x34b655…2a6f

18 touches
36 conflicts

0x324cb18b…bcc6

0x34b655…2a6f

12 touches
15 conflicts

0x641aed07…bcb9

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x57b02276…db3f

0x34b655…2a6f

6 touches
3 conflicts

0x8f203394…f2db

0x34b655…2a6f

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

36 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity