← previous blocknext block →recent activity

Analyzing

Block #94,867,374

20 transactions · 20 stateful · 2026-08-10 20:11:56 UTC

Parallelism

60/100

Blocked

40%

Avg conflicts / tx

1.15

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,867,374  ·  20 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

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x71e1dee6…d11b

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

6 touches
3 conflicts

0x7da6eb60…b34e

0x34b655…2a6f

4 touches
2 conflicts

0x8afd5bc5…28a5

0x34b655…2a6f

4 touches
1 conflict

0x945f18ee…b16d

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity