← previous blocknext block →recent activity

Analyzing

Block #94,792,521

18 transactions · 17 stateful · 2026-08-10 13:55:22 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.78

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,792,521  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf1f91cb6…3428

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xac8a5059…fd42

0x34b655…2a6f

6 touches
3 conflicts

0x08330b36…ae29

0x34b655…2a6f

6 touches
3 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

4 touches
1 conflict

0x0e22f39d…b92b

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x57b02276…db3f

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

3 conflicts on slot 0xf1f91cb619…f23428

← previous block·next block →recent activity