Block #73,210,620

← previous blocknext block →recent activity

Analyzing

Block #73,210,620

8 transactions · 8 stateful · 2026-05-08 09:06:03 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,210,620  ·  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

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb48a4f22…2da2

0x065c9d…c394

4 touches
1 conflict

0x195e0b23…1a93

0x065c9d…c394

3 touches
1 conflict

0x5dfcc982…6352

0x065c9d…c394

3 touches
1 conflict

0xc7b3f66e…3198

0x065c9d…c394

2 touches
0 conflicts

0xf3896d6a…8185

0x065c9d…c394

2 touches
0 conflicts

0xffc5cd88…2870

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 0xce7bfe5ef1…205e58

← previous block·next block →recent activity