← previous blocknext block →recent activity

Analyzing

Block #74,609,996

35 transactions · 29 stateful · 2026-05-14 20:44:01 UTC

Parallelism

69/100

Blocked

66%

Avg conflicts / tx

1.43

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,609,996  ·  35 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xa91c899f…6ee3

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x4ec9114f…44c2

0x34b655…2a6f

8 touches
6 conflicts

0x04f5363a…0c1c

0xd32edf…ff58

7 touches
6 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0x47b2d2eb…8aa5

0x34b655…2a6f

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

15 conflicts on slot 0xa91c899f02…fa6ee3

← previous block·next block →recent activity