← previous blocknext block →recent activity

Analyzing

Block #94,278,079

17 transactions · 16 stateful · 2026-08-08 18:36:54 UTC

Parallelism

47/100

Blocked

63%

Avg conflicts / tx

1.41

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #94,278,079  ·  17 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0x66bdb4c2…7ea6

0x34b655…2a6f

8 touches
6 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

6 touches
3 conflicts

0x291f491d…b156

0x34b655…2a6f

6 touches
3 conflicts

0x6771eae2…7014

0x34b655…2a6f

6 touches
3 conflicts

0x7ad017b4…f6fb

0x34b655…2a6f

6 touches
3 conflicts

0x897e8d63…0623

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity