← previous blocknext block →recent activity

Analyzing

Block #74,369,227

36 transactions · 19 stateful · 2026-05-13 17:53:46 UTC

Parallelism

83/100

Blocked

53%

Avg conflicts / tx

0.44

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,369,227  ·  36 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

0x2d4a115f…c83f

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2d10a2de…811f

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a568

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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 0x2d4a115fd6…07c83f

← previous block·next block →recent activity