← previous blocknext block →recent activity

Analyzing

Block #95,853,248

22 transactions · 18 stateful · 2026-08-14 07:06:08 UTC

Parallelism

68/100

Blocked

39%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,853,248  ·  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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x9a3463f0…0b73

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x9a8b7004…3e0a

0x34b655…2a6f

6 touches
3 conflicts

0x35a9f06c…7689

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x40a9339c…6572

0x34b655…2a6f

4 touches
1 conflict

0x53bda555…3810

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity