← previous blocknext block →recent activity

Analyzing

Block #94,807,683

20 transactions · 18 stateful · 2026-08-10 15:11:38 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,807,683  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf0d45ffd…89cf

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x529e53cf…38e4

0xa6afd3…d132

4 touches
1 conflict

0x989252a1…d812

0xa6afd3…d132

4 touches
1 conflict

0x183a32c3…5ef2

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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 0xf0d45ffdb0…4089cf

← previous block·next block →recent activity