← previous blocknext block →recent activity

Analyzing

Block #94,807,506

30 transactions · 25 stateful · 2026-08-10 15:10:45 UTC

Parallelism

63/100

Blocked

60%

Avg conflicts / tx

1.3

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #94,807,506  ·  30 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x95c47f03…f1bb

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0x428b6e5b…8909

0x34b655…2a6f

6 touches
3 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xabd0bcfc…64e2

0x34b655…2a6f

6 touches
3 conflicts

0x76d1e78d…7877

0x40c49f…2af0

6 touches
3 conflicts

0xd98b3c10…67b8

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

10 conflicts on slot 0x95c47f0322…51f1bb

← previous block·next block →recent activity