← previous blocknext block →recent activity

Analyzing

Block #74,770,399

25 transactions · 16 stateful · 2026-05-15 14:34:44 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.92

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,770,399  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x6c252583…27b9

0xd32edf…ff58

9 touches
10 conflicts

0x1f8a126c…9aa3

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0xe75ce681…ba60

0x188d58…ea8e

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: 0x754704bc…afb603

15 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity