← previous blocknext block →recent activity

Analyzing

Block #95,743,879

19 transactions · 19 stateful · 2026-08-13 21:56:03 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,743,879  ·  19 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

0xc85f42b6…6f23

0x34b655…2a6f

10 touches
10 conflicts

0x2dea5f07…8219

0x34b655…2a6f

6 touches
3 conflicts

0x08636046…e60f

0x34b655…2a6f

6 touches
3 conflicts

0x620b761c…270e

0x34b655…2a6f

6 touches
3 conflicts

0xf0d45ffd…89cf

0x34b655…2a6f

6 touches
3 conflicts

0x5d7e0e69…e6d2

0x34b655…2a6f

4 touches
1 conflict

0xd597209e…9800

0x34b655…2a6f

4 touches
1 conflict

0x6b71f2bb…f621

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

← previous block·next block →recent activity