← previous blocknext block →recent activity

Analyzing

Block #75,478,949

39 transactions · 32 stateful · 2026-05-18 21:27:59 UTC

Parallelism

64/100

Blocked

63%

Avg conflicts / tx

2.41

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #75,478,949  ·  39 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0x1054fdf2…f735

0xd32edf…ff58

23 touches
66 conflicts

0x00000000…0000

0xca50b9…1d03

10 touches
10 conflicts

0x8f1dbe88…8e36

0xee8c0e…1242

10 touches
10 conflicts

0x6320bc8e…f9a3

0xd18b7e…414b

10 touches
10 conflicts

0x00000000…0004

0xca50b9…1d03

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

6 touches
3 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

66 conflicts on slot 0x1054fdf258…93f735

← previous block·next block →recent activity