← previous blocknext block →recent activity

Analyzing

Block #75,478,948

38 transactions · 25 stateful · 2026-05-18 21:27:59 UTC

Parallelism

71/100

Blocked

68%

Avg conflicts / tx

1.63

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,478,948  ·  38 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xf4f5f2bd…2a5b

0xd32edf…ff58

17 touches
36 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x846f2172…fd54

0x0555e3…2b9c

8 touches
6 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

8 touches
6 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

8 touches
6 conflicts

0x5dfa485c…cf52

0x754704…b603

8 touches
6 conflicts

0x00000000…0000

0x9b60e5…f8ac

8 touches
6 conflicts

0x00000000…0004

0x9b60e5…f8ac

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: 0xd32edf66…9fff58

36 conflicts on slot 0xf4f5f2bdf4…2b2a5b

← previous block·next block →recent activity