← previous blocknext block →recent activity

Analyzing

Block #74,289,886

32 transactions · 21 stateful · 2026-05-13 09:06:01 UTC

Parallelism

66/100

Blocked

57%

Avg conflicts / tx

1.13

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,289,886  ·  32 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

0x39beb093…40af

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x5a3732cb…edac

0x1b6862…e19c

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

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

21 conflicts on slot 0x39beb09349…9840af

← previous block·next block →recent activity