← previous blocknext block →recent activity

Analyzing

Block #73,502,331

7 transactions · 6 stateful · 2026-05-09 17:26:56 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,502,331  ·  7 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

0x8a4a180e…9cbc

0x065c9d…c394

6 touches
3 conflicts

0x260fffc9…0e89

0x065c9d…c394

5 touches
3 conflicts

0xf2bbe568…792b

0x065c9d…c394

5 touches
3 conflicts

0x0175b7a6…1dbb

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbd

0x6c4bfa…a540

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x6c4bfa…a540

4 touches
1 conflict

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0xfc23dc3d…1b6a

0x065c9d…c394

4 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: 0x065c9d28…a9c394

3 conflicts on slot 0x8a4a180e9f…649cbc

← previous block·next block →recent activity