← previous blocknext block →recent activity

Analyzing

Block #95,244,764

22 transactions · 21 stateful · 2026-08-12 03:51:46 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,244,764  ·  22 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

0xb3fb9fb5…64db

0x34b655…2a6f

10 touches
10 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

6 touches
3 conflicts

0xafb8e71e…9285

0x34b655…2a6f

6 touches
3 conflicts

0x08636046…e60f

0x34b655…2a6f

6 touches
3 conflicts

0xfd196940…c22d

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x94542148…45ce

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 0xb3fb9fb561…7664db

← previous block·next block →recent activity