← previous blocknext block →recent activity

Analyzing

Block #74,252,326

35 transactions · 23 stateful · 2026-05-13 04:56:16 UTC

Parallelism

77/100

Blocked

70%

Avg conflicts / tx

1.46

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,252,326  ·  35 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

0x318ac0bb…6b9c

0x34b655…2a6f

12 touches
15 conflicts

0x2247cd31…8591

0xd32edf…ff58

11 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xfac61869…a562

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

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

15 conflicts on slot 0x318ac0bba0…ce6b9c

← previous block·next block →recent activity