← previous blocknext block →recent activity

Analyzing

Block #95,412,864

26 transactions · 19 stateful · 2026-08-12 18:09:48 UTC

Parallelism

77/100

Blocked

37%

Avg conflicts / tx

0.54

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,412,864  ·  26 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

0x3f2796bf…f0fa

0x34b655…2a6f

8 touches
6 conflicts

0x4bf59d22…00de

0x34b655…2a6f

6 touches
3 conflicts

0x2dd03fb9…6243

0x34b655…2a6f

4 touches
1 conflict

0x3a5cd535…3546

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2593

0x34b655…2a6f

4 touches
1 conflict

0x475bdffd…9a36

0x34b655…2a6f

4 touches
1 conflict

0x5e17e5be…d212

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

6 conflicts on slot 0x3f2796bf67…faf0fa

← previous block·next block →recent activity