← previous blocknext block →recent activity

Analyzing

Block #94,234,714

23 transactions · 21 stateful · 2026-08-08 14:57:02 UTC

Parallelism

61/100

Blocked

57%

Avg conflicts / tx

1.52

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #94,234,714  ·  23 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

14 touches
21 conflicts

0x00000000…00c9

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6426

0x34b655…2a6f

10 touches
10 conflicts

0x1d1f92db…ea61

0x34b655…2a6f

10 touches
10 conflicts

0x61d37f4f…61d2

0x34b655…2a6f

10 touches
10 conflicts

0x66bdb4c2…7ea6

0x34b655…2a6f

10 touches
10 conflicts

0x7aa5d2c4…d6ef

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity