← previous blocknext block →recent activity

Analyzing

Block #74,248,566

42 transactions · 34 stateful · 2026-05-13 04:31:20 UTC

Parallelism

81/100

Blocked

71%

Avg conflicts / tx

1.45

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,248,566  ·  42 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

0x5e9e41d2…a230

0xd32edf…ff58

15 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x768cffcd…2648

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0x91220b8f…7a08

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 0x5e9e41d2a6…8ba230

← previous block·next block →recent activity