← previous blocknext block →recent activity

Analyzing

Block #73,837,555

11 transactions · 10 stateful · 2026-05-11 06:53:31 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,837,555  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xef6ffd34…9b71

0xd32edf…ff58

5 touches
3 conflicts

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x20b1228b…2487

0x34b655…2a6f

2 touches
0 conflicts

0x50de0015…275c

0x34b655…2a6f

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

3 conflicts on slot 0xef6ffd341f…b49b71

← previous block·next block →recent activity