← previous blocknext block →recent activity

Analyzing

Block #74,638,430

21 transactions · 17 stateful · 2026-05-14 23:53:32 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.95

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,638,430  ·  21 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

0xe88bae98…f1eb

0xd32edf…ff58

9 touches
10 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x14af78bb…aedd

0x1b6862…e19c

6 touches
3 conflicts

0x968bdacb…f461

0x2a68ba…90c5

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

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 0xe88bae98d8…e0f1eb

← previous block·next block →recent activity