← previous blocknext block →recent activity

Analyzing

Block #73,807,308

12 transactions · 10 stateful · 2026-05-11 03:32:15 UTC

Parallelism

75/100

Blocked

20%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,807,308  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x490911cc…5fea

0x0c65a0…0852

2 touches
0 conflicts

0x85946e90…7fd6

0x0c65a0…0852

2 touches
0 conflicts

0xaf41644f…8f2e

0x0c65a0…0852

2 touches
0 conflicts

0x373f94db…c177

0x3bd359…433a

2 touches
0 conflicts

0x3de215fe…c018

0x3bd359…433a

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity