← previous blocknext block →recent activity

Analyzing

Block #75,948,698

29 transactions · 24 stateful · 2026-05-21 01:48:14 UTC

Parallelism

72/100

Blocked

67%

Avg conflicts / tx

1.86

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,948,698  ·  29 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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x443a3e47…f4a4

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity