Block #73,658,027

← previous blocknext block →recent activity

Analyzing

Block #73,658,027

11 transactions · 10 stateful · 2026-05-10 10:45:18 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,658,027  ·  11 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x465dc2be…777f

0x065c9d…c394

4 touches
1 conflict

0x32cc4bc6…5fab

0x065c9d…c394

3 touches
1 conflict

0xdfb3aaae…2a47

0x065c9d…c394

3 touches
1 conflict

0x1f37f0fc…5dff

0x065c9d…c394

3 touches
1 conflict

0x4040be25…a9a9

0x065c9d…c394

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity