← previous blocknext block →recent activity

Analyzing

Block #95,783,450

20 transactions · 19 stateful · 2026-08-14 01:15:03 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,783,450  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x4efae872…6aa8

0x34b655…2a6f

8 touches
6 conflicts

0x151a39c9…e8e2

0x34b655…2a6f

8 touches
6 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0x4d5053d1…3b7d

0x34b655…2a6f

4 touches
1 conflict

0x815c518b…2ff4

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

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 0xc824469a90…af6425

← previous block·next block →recent activity