Block #73,473,755

← previous blocknext block →recent activity

Analyzing

Block #73,473,755

8 transactions · 8 stateful · 2026-05-09 14:16:43 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,473,755  ·  8 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x0e9f17dd…a6c0

0x065c9d…c394

2 touches
0 conflicts

0x13326c3d…fc8d

0x065c9d…c394

2 touches
0 conflicts

0x75c9c7ad…6d7c

0x065c9d…c394

2 touches
0 conflicts

0xde4d5df4…f929

0x065c9d…c394

2 touches
0 conflicts

0xe001c2f7…af86

0x065c9d…c394

2 touches
0 conflicts

0xf537eaa0…73c8

0x065c9d…c394

2 touches
0 conflicts

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity