← previous blocknext block →recent activity

Analyzing

Block #74,440,110

22 transactions · 18 stateful · 2026-05-14 01:45:40 UTC

Parallelism

77/100

Blocked

39%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,440,110  ·  22 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

0xca6ae467…1120

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x4d42f16e…a6c9

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0xd49762c9…1359

0x34b655…2a6f

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

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: 0xd32edf66…9fff58

10 conflicts on slot 0xca6ae467cc…821120

← previous block·next block →recent activity