← previous blocknext block →recent activity

Analyzing

Block #74,527,249

42 transactions · 30 stateful · 2026-05-14 11:27:42 UTC

Parallelism

83/100

Blocked

57%

Avg conflicts / tx

0.98

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,527,249  ·  42 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

0xf2c0bd50…4454

0xd32edf…ff58

11 touches
15 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xcb45d9d6…cb85

0x1b6862…e19c

8 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

8 touches
6 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

15 conflicts on slot 0xf2c0bd50b0…914454

← previous block·next block →recent activity