Block #73,744,438

← previous blocknext block →recent activity

Analyzing

Block #73,744,438

16 transactions · 11 stateful · 2026-05-10 20:28:21 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,744,438  ·  16 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

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0xc5315da6…0e37

0x065c9d…c394

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xaa8a1c54…ead3

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x2e2214a9…fe0d

0x6c4bfa…a540

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x6c4bfa…a540

4 touches
1 conflict

0xe7535190…5a0f

0x6c4bfa…a540

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 0xed57bddf8e…bd1abf

← previous block·next block →recent activity