← previous blocknext block →recent activity

Analyzing

Block #73,506,335

8 transactions · 7 stateful · 2026-05-09 17:53:40 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,506,335  ·  8 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x2a823462…e0d2

0x065c9d…c394

4 touches
1 conflict

0x0b998a39…39c4

0x065c9d…c394

2 touches
0 conflicts

0xac22227d…9e5c

0x065c9d…c394

2 touches
0 conflicts

0xc4959cb2…777e

0x065c9d…c394

2 touches
0 conflicts

0xcd626f8b…12af

0x065c9d…c394

2 touches
0 conflicts

0xe0037741…33ac

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity