← previous blocknext block →recent activity

Analyzing

Block #74,647,049

28 transactions · 21 stateful · 2026-05-15 00:50:57 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,647,049  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0028c412…a8c6

0xd32edf…ff58

9 touches
10 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0x03f9cc30…b46c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

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

10 conflicts on slot 0x0028c41214…a2a8c6

← previous block·next block →recent activity