← previous blocknext block →recent activity

Analyzing

Block #74,423,281

30 transactions · 26 stateful · 2026-05-13 23:53:36 UTC

Parallelism

73/100

Blocked

69%

Avg conflicts / tx

1.6

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,423,281  ·  30 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

0xc4b90466…3f9a

0xd32edf…ff58

15 touches
28 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x6aa624fd…a84e

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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

28 conflicts on slot 0xc4b9046641…403f9a

← previous block·next block →recent activity