← previous blocknext block →recent activity

Analyzing

Block #94,718,795

21 transactions · 18 stateful · 2026-08-10 07:43:03 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,718,795  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbf78ee7f…e7fd

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe3f67d6c…a1aa

0x34b655…2a6f

4 touches
1 conflict

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x324ec4d3…f156

0x34b655…2a6f

4 touches
1 conflict

0x51087f5a…61f7

0x34b655…2a6f

4 touches
1 conflict

0x5c16527f…628c

0x34b655…2a6f

4 touches
1 conflict

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 0xbf78ee7fb5…b5e7fd

← previous block·next block →recent activity