← previous blocknext block →recent activity

Analyzing

Block #74,034,022

13 transactions · 12 stateful · 2026-05-12 04:43:59 UTC

Parallelism

62/100

Blocked

58%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,034,022  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8d3166c4…7cfb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0f9b918b…212d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5a838048…8ba4

0xd32edf…ff58

5 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

3 conflicts on slot 0x8d3166c4fa…257cfb

← previous block·next block →recent activity