← previous blocknext block →recent activity

Analyzing

Block #73,977,759

15 transactions · 11 stateful · 2026-05-11 22:27:40 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,977,759  ·  15 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21c1

0x1b6862…e19c

2 touches
0 conflicts

0x4bef88e0…eaca

0x3bd359…433a

2 touches
0 conflicts

0xc5c4c1d1…2145

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity