← previous blocknext block →recent activity

Analyzing

Block #74,332,193

30 transactions · 22 stateful · 2026-05-13 13:47:27 UTC

Parallelism

87/100

Blocked

45%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,332,193  ·  30 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

0xf339ce5f…4abc

0xd32edf…ff58

7 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xba5743c7…21c0

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

6 touches
3 conflicts

0xa94cf3f4…554c

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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

6 conflicts on slot 0xf339ce5fb9…de4abc

← previous block·next block →recent activity