← previous blocknext block →recent activity

Analyzing

Block #95,074,562

22 transactions · 20 stateful · 2026-08-11 13:34:50 UTC

Parallelism

68/100

Blocked

45%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,074,562  ·  22 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

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

8 touches
6 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x56b580bf…f969

0x34b655…2a6f

4 touches
1 conflict

0xafb8e71e…9285

0x34b655…2a6f

4 touches
1 conflict

0x1d73754c…2e95

0x34b655…2a6f

4 touches
1 conflict

0x8eef368f…aa21

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 0xec7d120df9…5d7084

← previous block·next block →recent activity