← previous blocknext block →recent activity

Analyzing

Block #73,389,044

9 transactions · 8 stateful · 2026-05-09 04:52:55 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.67

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,389,044  ·  9 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xc41322f8…1dc8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9bbbdda8…176d

0x065c9d…c394

3 touches
1 conflict

0x4f7b1ad1…f989

0x065c9d…c394

3 touches
1 conflict

0x5a680739…bd42

0x065c9d…c394

3 touches
1 conflict

0xf4d8cf49…c446

0x065c9d…c394

3 touches
1 conflict

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity