← previous blocknext block →recent activity

Analyzing

Block #73,390,302

11 transactions · 10 stateful · 2026-05-09 05:01:18 UTC

Parallelism

64/100

Blocked

30%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,390,302  ·  11 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x03833adf…b96f

0x065c9d…c394

4 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x3e15d15d…2ebb

0x065c9d…c394

2 touches
0 conflicts

0x43bd830e…c628

0x065c9d…c394

2 touches
0 conflicts

0x8eefbc5e…e055

0x065c9d…c394

2 touches
0 conflicts

0x4ae4b486…d0ec

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity