Block #73,211,641

← previous blocknext block →recent activity

Analyzing

Block #73,211,641

10 transactions · 10 stateful · 2026-05-08 09:12:46 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,211,641  ·  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

0x59dafff6…4a7c

0x065c9d…c394

4 touches
1 conflict

0x44db0e4b…2a2f

0x065c9d…c394

3 touches
1 conflict

0xefb2095a…b9e5

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x4d2baf4f…51dd

0x065c9d…c394

2 touches
0 conflicts

0x58fcfdc3…421b

0x065c9d…c394

2 touches
0 conflicts

0x7f189cf6…afab

0x065c9d…c394

2 touches
0 conflicts

0xc41c1ecf…6e50

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 0x59dafff632…2d4a7c

← previous block·next block →recent activity