← previous blocknext block →recent activity

Analyzing

Block #74,609,359

44 transactions · 31 stateful · 2026-05-14 20:39:47 UTC

Parallelism

80/100

Blocked

68%

Avg conflicts / tx

1.48

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,609,359  ·  44 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x409d9a69…6e6c

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xba5743c7…21c6

0x1b6862…e19c

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

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

28 conflicts on slot 0x409d9a69ef…d16e6c

← previous block·next block →recent activity