← previous blocknext block →recent activity

Analyzing

Block #73,384,151

20 transactions · 14 stateful · 2026-05-09 04:20:23 UTC

Parallelism

80/100

Blocked

43%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,384,151  ·  20 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

0xc227c7d5…e49e

0xd32edf…ff58

7 touches
6 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0x8ccae6bc…d161

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

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

6 conflicts on slot 0xc227c7d5d3…c6e49e

← previous block·next block →recent activity