← previous blocknext block →recent activity

Analyzing

Block #95,114,297

16 transactions · 15 stateful · 2026-08-11 16:54:44 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,114,297  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

6 touches
3 conflicts

0xe8eae8a3…bacc

0x34b655…2a6f

6 touches
3 conflicts

0x6b6e8f7c…988a

0x34b655…2a6f

4 touches
1 conflict

0x86977b3d…a9c4

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0xa45116ed…5331

0x34b655…2a6f

4 touches
1 conflict

0xb10b0390…fa46

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity