← previous blocknext block →recent activity

Analyzing

Block #73,383,819

12 transactions · 10 stateful · 2026-05-09 04:18:10 UTC

Parallelism

67/100

Blocked

30%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,383,819  ·  12 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

0xb159af88…a9e7

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0bc1d651…575f

0x065c9d…c394

3 touches
1 conflict

0x9a0d1cab…34c1

0x065c9d…c394

2 touches
0 conflicts

0xf9a1a99b…9643

0x065c9d…c394

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

6 conflicts on slot 0xb159af880b…47a9e7

← previous block·next block →recent activity