← previous blocknext block →recent activity

Analyzing

Block #74,204,432

36 transactions · 27 stateful · 2026-05-12 23:37:50 UTC

Parallelism

78/100

Blocked

59%

Avg conflicts / tx

1.47

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,204,432  ·  36 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x1b0792ac…70d2

0xd32edf…ff58

13 touches
21 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

10 touches
10 conflicts

0x0a6cb118…4ca9

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

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: 0x34b6552d…112a6f

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity