← previous blocknext block →recent activity

Analyzing

Block #74,609,450

22 transactions · 16 stateful · 2026-05-14 20:40:23 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,609,450  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x31e54df3…6f28

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x14d1bf0e…e0a0

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x0772fc46…a916

0x34b655…2a6f

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

4 touches
1 conflict

0x1697794d…fd34

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

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 0x31e54df389…f56f28

← previous block·next block →recent activity