← previous blocknext block →recent activity

Analyzing

Block #73,490,628

7 transactions · 7 stateful · 2026-05-09 16:09:04 UTC

Parallelism

71/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,490,628  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1e2b5d88…c19b

0x065c9d…c394

4 touches
1 conflict

0xe20db839…7577

0x065c9d…c394

4 touches
1 conflict

0xe25c9b29…3290

0x065c9d…c394

3 touches
1 conflict

0xf09826df…de31

0x065c9d…c394

3 touches
1 conflict

0x3147ceab…8c60

0x065c9d…c394

3 touches
1 conflict

0x72b8e38c…ec83

0x065c9d…c394

3 touches
1 conflict

0x9c97dfc6…9bb9

0x065c9d…c394

2 touches
0 conflicts

0xc1f20688…940d

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

1 conflict on slot 0x1e2b5d88f2…e1c19b

← previous block·next block →recent activity