Block #73,641,716

← previous blocknext block →recent activity

Analyzing

Block #73,641,716

8 transactions · 7 stateful · 2026-05-10 08:55:20 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,641,716  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x3cdfc713…a263

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0dffd869…f0b9

0x065c9d…c394

3 touches
1 conflict

0xa89a0eab…17ed

0x065c9d…c394

2 touches
0 conflicts

0xc825c88a…189a

0x065c9d…c394

2 touches
0 conflicts

0xd7b31fb8…fe40

0x065c9d…c394

2 touches
0 conflicts

0xed6493d2…f8c9

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity