← previous blocknext block →recent activity

Analyzing

Block #74,353,279

28 transactions · 21 stateful · 2026-05-13 16:07:38 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.64

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,353,279  ·  28 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

0x38ff56ba…7e77

0xd32edf…ff58

9 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c0

0x1b6862…e19c

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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

10 conflicts on slot 0x38ff56bad3…847e77

← previous block·next block →recent activity