← previous blocknext block →recent activity

Analyzing

Block #94,684,491

17 transactions · 17 stateful · 2026-08-10 04:50:32 UTC

Parallelism

35/100

Blocked

65%

Avg conflicts / tx

3.82

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #94,684,491  ·  17 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

22 touches
55 conflicts

0x482471ad…122f

0x34b655…2a6f

18 touches
36 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0x948836ff…59ab

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xf3383813…4a0c

0x34b655…2a6f

8 touches
6 conflicts

0xcbfeb997…6e11

0x34b655…2a6f

6 touches
4 conflicts

0x25429022…758c

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

55 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity