← previous blocknext block →recent activity

Analyzing

Block #94,869,921

24 transactions · 20 stateful · 2026-08-10 20:24:45 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,869,921  ·  24 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

0x216ffe66…1f94

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x74d6c8dd…1695

0x34b655…2a6f

6 touches
3 conflicts

0x670b8bb6…cd46

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xe483d4e3…e52f

0x1b6862…e19c

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

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 0x216ffe6648…bf1f94

← previous block·next block →recent activity