← previous blocknext block →recent activity

Analyzing

Block #73,468,911

17 transactions · 16 stateful · 2026-05-09 13:44:31 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,468,911  ·  17 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

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x02d67723…1743

0x34b655…2a6f

4 touches
1 conflict

0x0e5611e4…8065

0x34b655…2a6f

4 touches
1 conflict

0x0f20e35b…511d

0x34b655…2a6f

4 touches
1 conflict

0x1d1799a9…c621

0x34b655…2a6f

4 touches
1 conflict

0x20be24f0…d26a

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: 0x065c9d28…a9c394

3 conflicts on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity