← previous blocknext block →recent activity

Analyzing

Block #73,035,538

23 transactions · 18 stateful · 2026-05-07 13:41:03 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,035,538  ·  23 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

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x5dc14a96…6816

0x34b655…2a6f

4 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0x7b50a82b…f53d

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: 0x681e908b…e1ae09

6 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity