← previous blocknext block →recent activity

Analyzing

Block #95,375,462

23 transactions · 21 stateful · 2026-08-12 15:00:29 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

0.83

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,375,462  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x08636046…e60f

0x34b655…2a6f

8 touches
6 conflicts

0x53f393fa…00b9

0x34b655…2a6f

8 touches
6 conflicts

0x16ef6aaa…6eb2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xafb8e71e…9285

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x921a58d1…db22

0x34b655…2a6f

4 touches
1 conflict

0xaae6463e…bfcc

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 0x08636046fc…69e60f

← previous block·next block →recent activity