← previous blocknext block →recent activity

Analyzing

Block #94,685,271

20 transactions · 18 stateful · 2026-08-10 04:54:27 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #94,685,271  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x90d93553…b73a

0x34b655…2a6f

8 touches
6 conflicts

0xe2e52e46…0894

0x34b655…2a6f

8 touches
6 conflicts

0x217bd767…b79e

0x34b655…2a6f

4 touches
1 conflict

0x23a320fb…cbd7

0x34b655…2a6f

4 touches
1 conflict

0x3c0d2f30…1afb

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: Perpl

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity