← previous blocknext block →recent activity

Analyzing

Block #95,126,481

21 transactions · 18 stateful · 2026-08-11 17:56:01 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,126,481  ·  21 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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x8cd684d0…c3cb

0x34b655…2a6f

6 touches
3 conflicts

0x3de775b2…319b

0xa6afd3…d132

4 touches
1 conflict

0x2bb0d58d…9dcf

0x34b655…2a6f

4 touches
1 conflict

0x006972c1…db66

0x34b655…2a6f

4 touches
1 conflict

0x4295a3f8…97a1

0x34b655…2a6f

4 touches
1 conflict

0x4d4e1c79…d38e

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

3 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity