← previous blocknext block →recent activity

Analyzing

Block #73,384,221

11 transactions · 11 stateful · 2026-05-09 04:20:51 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.64

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,384,221  ·  11 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

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xa4d8bd9e…631f

0x065c9d…c394

2 touches
0 conflicts

0xb24a31ca…6b4a

0x065c9d…c394

2 touches
0 conflicts

0xd95cb02e…7b8e

0x065c9d…c394

2 touches
0 conflicts

0xeeb8ee7c…009f

0x065c9d…c394

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

3 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity