← previous blocknext block →recent activity

Analyzing

Block #94,678,585

21 transactions · 16 stateful · 2026-08-10 04:20:48 UTC

Parallelism

81/100

Blocked

50%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,678,585  ·  21 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

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf3383813…4a0c

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x0140fbd3…d957

0x34b655…2a6f

4 touches
1 conflict

0x0f2d78b1…7363

0x34b655…2a6f

4 touches
1 conflict

0x1b4fa1a0…7d7b

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

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

1 conflict on slot 0xca841faae5…71486a

← previous block·next block →recent activity