← previous blocknext block →recent activity

Analyzing

Block #94,758,911

22 transactions · 21 stateful · 2026-08-10 11:06:19 UTC

Parallelism

68/100

Blocked

52%

Avg conflicts / tx

1.36

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,758,911  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe2e52e46…0894

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x4eb691ce…350c

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6426

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 0xe2e52e4663…6f0894

← previous block·next block →recent activity