Block #73,917,621

← previous blocknext block →recent activity

Analyzing

Block #73,917,621

10 transactions · 10 stateful · 2026-05-11 15:47:06 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,917,621  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x0ee25e11…97af

0x065c9d…c394

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x29a0d349…578f

0x065c9d…c394

3 touches
1 conflict

0xb145276d…acab

0x065c9d…c394

3 touches
1 conflict

0xc7a7417f…bce0

0x065c9d…c394

2 touches
0 conflicts

0xd851d98d…bc6f

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity