← previous blocknext block →recent activity

Analyzing

Block #73,043,074

32 transactions · 22 stateful · 2026-05-07 14:31:13 UTC

Parallelism

88/100

Blocked

36%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,043,074  ·  32 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

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf150be3e…dd23

0xd32edf…ff58

5 touches
3 conflicts

0xac2a0273…7212

0x34b655…2a6f

4 touches
1 conflict

0xce7bfe5e…5e58

0x065c9d…c394

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

2 touches
0 conflicts

0xf853eb8e…401e

0x34b655…2a6f

2 touches
0 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

2 touches
0 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: 0x681e908b…e1ae09

6 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity