← previous blocknext block →recent activity

Analyzing

Block #95,075,299

22 transactions · 17 stateful · 2026-08-11 13:38:32 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,075,299  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf9e23360…8ef7

0x34b655…2a6f

8 touches
6 conflicts

0xac3e4969…39e9

0x34b655…2a6f

6 touches
3 conflicts

0x08636046…e60f

0x34b655…2a6f

6 touches
3 conflicts

0x4ad890f0…5ac0

0x34b655…2a6f

4 touches
1 conflict

0x4be9812b…48a9

0x34b655…2a6f

4 touches
1 conflict

0x4cabb80a…46bf

0x34b655…2a6f

4 touches
1 conflict

0x5c137637…d078

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

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

6 conflicts on slot 0xf9e23360ff…e88ef7

← previous block·next block →recent activity