← previous blocknext block →recent activity

Analyzing

Block #73,960,499

9 transactions · 7 stateful · 2026-05-11 20:32:17 UTC

Parallelism

56/100

Blocked

43%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,960,499  ·  9 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

0x6a5ec735…6d49

0x065c9d…c394

3 touches
1 conflict

0xb73c3f96…9d71

0x065c9d…c394

3 touches
1 conflict

0xbb086809…4937

0x065c9d…c394

3 touches
1 conflict

0x3cdd3687…64b7

0x065c9d…c394

2 touches
0 conflicts

0x44409252…6917

0x065c9d…c394

2 touches
0 conflicts

0x94782c23…6df1

0x065c9d…c394

2 touches
0 conflicts

0xb320426d…cd57

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