← previous blocknext block →recent activity

Analyzing

Block #73,970,728

9 transactions · 5 stateful · 2026-05-11 21:40:26 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,970,728  ·  9 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x2ff40e93…a40c

0xd32edf…ff58

3 touches
1 conflict

0x512973f9…9731

0x065c9d…c394

3 touches
1 conflict

0xdb315203…5ce9

0x065c9d…c394

3 touches
1 conflict

0xf39e38d0…dd30

0x065c9d…c394

3 touches
1 conflict

0x61882bd9…74d5

0x065c9d…c394

2 touches
0 conflicts

0x7680ee17…7234

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity