Block #73,744,441

← previous blocknext block →recent activity

Analyzing

Block #73,744,441

20 transactions · 15 stateful · 2026-05-10 20:28:22 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,744,441  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x0ac31945…2c72

0x065c9d…c394

8 touches
6 conflicts

0xaa8a1c54…ead3

0x34b655…2a6f

4 touches
1 conflict

0x194f2c02…19e6

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb2b4ae24…12ed

0x34b655…2a6f

4 touches
1 conflict

0xdf616111…b85f

0x065c9d…c394

3 touches
1 conflict

0x8f2c0a6b…aefb

0xd32edf…ff58

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity