← previous blocknext block →recent activity

Analyzing

Block #95,074,113

20 transactions · 19 stateful · 2026-08-11 13:32:34 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,074,113  ·  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

0x734ee320…caae

0x34b655…2a6f

10 touches
10 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0x34731dbd…e467

0x34b655…2a6f

4 touches
1 conflict

0x36890fff…f3d1

0x34b655…2a6f

4 touches
1 conflict

0x4cabb80a…46bf

0x34b655…2a6f

4 touches
1 conflict

0x5da59c2b…d7b2

0x34b655…2a6f

4 touches
1 conflict

0x9c1e34a2…a218

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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 0x734ee32053…cecaae

← previous block·next block →recent activity