← previous blocknext block →recent activity

Analyzing

Block #74,774,261

32 transactions · 26 stateful · 2026-05-15 15:00:35 UTC

Parallelism

75/100

Blocked

62%

Avg conflicts / tx

1.31

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,774,261  ·  32 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

0x5964c104…6746

0xd32edf…ff58

13 touches
21 conflicts

0x3e49348b…9445

0x34b655…2a6f

10 touches
10 conflicts

0xba5743c7…21c1

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

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 0x5964c1048d…066746

← previous block·next block →recent activity