← previous blocknext block →recent activity

Analyzing

Block #73,655,106

32 transactions · 23 stateful · 2026-05-10 10:25:35 UTC

Parallelism

84/100

Blocked

52%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,655,106  ·  32 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

0x1f0e08ef…acdf

0xd32edf…ff58

9 touches
10 conflicts

0x9a43401f…9d06

0x34b655…2a6f

8 touches
6 conflicts

0x2877f440…c2c8

0x34b655…2a6f

8 touches
6 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xef17b8cd…9511

0x34b655…2a6f

8 touches
6 conflicts

0xf2438038…5fa7

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

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

10 conflicts on slot 0x1f0e08ef84…7bacdf

← previous block·next block →recent activity