← previous blocknext block →recent activity

Analyzing

Block #94,220,784

19 transactions · 17 stateful · 2026-08-08 13:46:18 UTC

Parallelism

58/100

Blocked

59%

Avg conflicts / tx

1.53

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,220,784  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…00c9

0x34b655…2a6f

8 touches
6 conflicts

0x66bdb4c2…7ea6

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

8 touches
6 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x7462b8f2…6312

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 0xc824469a90…af6425

← previous block·next block →recent activity