← previous blocknext block →recent activity

Analyzing

Block #73,639,250

34 transactions · 27 stateful · 2026-05-10 08:38:49 UTC

Parallelism

82/100

Blocked

56%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,639,250  ·  34 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7254dddd…2d7a

0xd32edf…ff58

11 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0xb81d3ee7…3947

0x34b655…2a6f

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x09beabbc…065e

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

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

15 conflicts on slot 0x7254dddda0…f62d7a

← previous block·next block →recent activity