← previous blocknext block →recent activity

Analyzing

Block #73,383,884

14 transactions · 13 stateful · 2026-05-09 04:18:36 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,383,884  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xa51f1267…9a1e

0x065c9d…c394

4 touches
1 conflict

0x4a716a25…0cd1

0x065c9d…c394

3 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

2 touches
0 conflicts

0xe038916c…b1be

0x2a68ba…90c5

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity