Block #73,960,494

← previous blocknext block →recent activity

Analyzing

Block #73,960,494

10 transactions · 6 stateful · 2026-05-11 20:32:15 UTC

Parallelism

80/100

Blocked

17%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,960,494  ·  10 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xef3f9c1d…da47

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0655ca7e…2676

0x065c9d…c394

2 touches
0 conflicts

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity