← previous blocknext block →recent activity

Analyzing

Block #74,352,438

21 transactions · 15 stateful · 2026-05-13 16:02:02 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,352,438  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x739fdfac…02a4

0xd32edf…ff58

5 touches
3 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

4 touches
1 conflict

0x104887dc…9894

0x34b655…2a6f

4 touches
1 conflict

0x1bde0d88…9fcf

0x34b655…2a6f

4 touches
1 conflict

0x8e594d49…0f8f

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0x8c49c85c3e…afee96

← previous block·next block →recent activity