← previous blocknext block →recent activity

Analyzing

Block #73,210,927

8 transactions · 8 stateful · 2026-05-08 09:08:03 UTC

Parallelism

75/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,210,927  ·  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

0x8c2da147…c8c0

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xcd6de2ad…dfd7

0x065c9d…c394

3 touches
1 conflict

0xf6b7aafa…2fc2

0x065c9d…c394

3 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

2 touches
0 conflicts

0x64979bde…ba46

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 0x8c2da1471f…37c8c0

← previous block·next block →recent activity