← previous blocknext block →recent activity

Analyzing

Block #74,765,282

33 transactions · 22 stateful · 2026-05-15 14:00:24 UTC

Parallelism

73/100

Blocked

68%

Avg conflicts / tx

1.48

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,765,282  ·  33 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x9f51d6e7…be77

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x6fd9ae7c…e97f

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

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

36 conflicts on slot 0x9f51d6e78f…2fbe77

← previous block·next block →recent activity