← previous blocknext block →recent activity

Analyzing

Block #94,668,114

21 transactions · 20 stateful · 2026-08-10 03:28:09 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,668,114  ·  21 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

0x76d1e78d…7877

0x40c49f…2af0

6 touches
3 conflicts

0x2c2db8e9…fdc7

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x30c5329c…711c

0x34b655…2a6f

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: 0x40c49f17…d22af0

3 conflicts on slot 0x76d1e78d12…117877

← previous block·next block →recent activity