← previous blocknext block →recent activity

Analyzing

Block #74,920,074

45 transactions · 33 stateful · 2026-05-16 07:13:16 UTC

Parallelism

76/100

Blocked

61%

Avg conflicts / tx

1.42

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,920,074  ·  45 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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x26bb6db7…f861

0x1b6862…e19c

10 touches
10 conflicts

0x417609f7…b021

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…001d

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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity