← previous blocknext block →recent activity

Analyzing

Block #94,974,089

16 transactions · 16 stateful · 2026-08-11 05:08:39 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.81

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,974,089  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x216ffe66…1f94

0x34b655…2a6f

6 touches
3 conflicts

0x524f0872…0d12

0x34b655…2a6f

6 touches
3 conflicts

0x2b5101ac…090b

0x34b655…2a6f

6 touches
3 conflicts

0x4bfbd222…8aa7

0x34b655…2a6f

6 touches
3 conflicts

0x511cdf65…47ab

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xcfd12832…e024

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity