Block #73,643,849

← previous blocknext block →recent activity

Analyzing

Block #73,643,849

12 transactions · 10 stateful · 2026-05-10 09:09:46 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,643,849  ·  12 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

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x61c3475e…14df

0x065c9d…c394

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x8a2657f5…e008

0x34b655…2a6f

4 touches
1 conflict

0xa6f92ae5…62c6

0x065c9d…c394

3 touches
1 conflict

0xd3428926…92be

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

6 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity