← previous blocknext block →recent activity

Analyzing

Block #95,008,404

24 transactions · 21 stateful · 2026-08-11 08:01:15 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,008,404  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x11b69a7e…334e

0x01bff4…1071

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x05527801…9c11

0x34b655…2a6f

4 touches
1 conflict

0x33ecd98b…29cb

0x34b655…2a6f

4 touches
1 conflict

0x71e9fe9f…2ad6

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8e19cc0c…b765

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: 0x01bff417…bc1071

3 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity