← previous blocknext block →recent activity

Analyzing

Block #94,905,480

19 transactions · 19 stateful · 2026-08-10 23:23:35 UTC

Parallelism

79/100

Blocked

37%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,905,480  ·  19 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

0x22e2efd1…ae3d

0x34b655…2a6f

6 touches
3 conflicts

0x07b86c51…cdae

0x2a68ba…90c5

6 touches
3 conflicts

0xe9452241…95a3

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x2deb0633…4a7c

0x851145…3f07

5 touches
3 conflicts

0x9fd37234…2731

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

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 0x22e2efd10c…d5ae3d

← previous block·next block →recent activity