← previous blocknext block →recent activity

Analyzing

Block #73,176,233

14 transactions · 13 stateful · 2026-05-08 05:17:01 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,176,233  ·  14 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

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0x2655dabd…d080

0x065c9d…c394

4 touches
1 conflict

0x2a354a63…0515

0x065c9d…c394

4 touches
1 conflict

0x8e66da19…66b6

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0xe09eda07…8dda

0x2a68ba…90c5

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: 0xc8689a47…62ee79

1 conflict on slot 0x4e5ebbf7fb…3fae70

← previous block·next block →recent activity