← previous blocknext block →recent activity

Analyzing

Block #94,304,378

18 transactions · 17 stateful · 2026-08-08 20:49:58 UTC

Parallelism

61/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,304,378  ·  18 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xa3f095f5…bd87

0x34b655…2a6f

8 touches
6 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

6 touches
3 conflicts

0x1cc14c11…dc1c

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x26b24ca7…abf6

0x34b655…2a6f

4 touches
1 conflict

0x32409e80…a396

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 0xc824469a90…af6425

← previous block·next block →recent activity