← previous blocknext block →recent activity

Analyzing

Block #74,304,559

27 transactions · 22 stateful · 2026-05-13 10:43:41 UTC

Parallelism

70/100

Blocked

73%

Avg conflicts / tx

1.41

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,304,559  ·  27 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

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

8 touches
6 conflicts

0x1cb0ec5e…28ae

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x318ac0bb…6b9c

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity