← previous blocknext block →recent activity

Analyzing

Block #94,170,803

16 transactions · 16 stateful · 2026-08-08 09:33:00 UTC

Parallelism

44/100

Blocked

63%

Avg conflicts / tx

1.81

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #94,170,803  ·  16 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xb409e204…89ac

0x34b655…2a6f

10 touches
10 conflicts

0xc0defe91…fe26

0x34b655…2a6f

7 touches
6 conflicts

0xde95b18d…3751

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0x349f436e…80e6

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

15 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity