← previous blocknext block →recent activity

Analyzing

Block #95,721,605

17 transactions · 16 stateful · 2026-08-13 20:04:01 UTC

Parallelism

65/100

Blocked

38%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,721,605  ·  17 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

0xc85f42b6…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xe2ca9bf2…8da8

0x34b655…2a6f

6 touches
3 conflicts

0x7252e3f2…a7fe

0x34b655…2a6f

6 touches
3 conflicts

0xb2fa1675…4e07

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x620b761c…270e

0x34b655…2a6f

6 touches
3 conflicts

0x923c9dce…e69a

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eeb

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 0xc85f42b605…b36f23

← previous block·next block →recent activity