Block #73,353,222

← previous blocknext block →recent activity

Analyzing

Block #73,353,222

16 transactions · 12 stateful · 2026-05-09 00:54:46 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,353,222  ·  16 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

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0xdc6f5579…e5ed

0x065c9d…c394

4 touches
1 conflict

0xbdff944d…447e

0x2a68ba…90c5

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x8a35acfb…d1ae

0x8d66a4…3095

4 touches
1 conflict

0x46b2728f…a83b

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