← previous blocknext block →recent activity

Analyzing

Block #73,034,950

16 transactions · 13 stateful · 2026-05-07 13:37:09 UTC

Parallelism

81/100

Blocked

23%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,034,950  ·  16 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

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x832df688…31bc

0x065c9d…c394

5 touches
3 conflicts

0x23d07465…928b

0x065c9d…c394

5 touches
3 conflicts

0x6ac9faaf…89f9

0x065c9d…c394

5 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x3702b140…97ea

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 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity