← previous blocknext block →recent activity

Analyzing

Block #73,308,241

8 transactions · 7 stateful · 2026-05-08 19:55:24 UTC

Parallelism

38/100

Blocked

57%

Avg conflicts / tx

1.25

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,308,241  ·  8 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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3a1d7033…1395

0x065c9d…c394

2 touches
0 conflicts

0x4882f28c…1ce1

0x065c9d…c394

2 touches
0 conflicts

0xe8706327…1ce1

0x065c9d…c394

2 touches
0 conflicts

0x09106a95…1467

0xeedfbc…f7dc

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity