← previous blocknext block →recent activity

Analyzing

Block #74,353,120

33 transactions · 25 stateful · 2026-05-13 16:06:34 UTC

Parallelism

67/100

Blocked

64%

Avg conflicts / tx

1.85

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,353,120  ·  33 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

0x62d080e9…4a7c

0x34b655…2a6f

14 touches
21 conflicts

0x1b71cc48…7772

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0019

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0029

0x1b6862…e19c

12 touches
15 conflicts

0x485d2778…aa5b

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 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 0x62d080e928…5a4a7c

← previous block·next block →recent activity