← previous blocknext block →recent activity

Analyzing

Block #73,035,569

25 transactions · 22 stateful · 2026-05-07 13:41:15 UTC

Parallelism

76/100

Blocked

64%

Avg conflicts / tx

1.2

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,035,569  ·  25 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xdaca243a…f9de

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xd574ca…7ab1

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x829c0589…3d33

0x065c9d…c394

5 touches
3 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

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: 0x34b6552d…112a6f

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity