← previous blocknext block →recent activity

Analyzing

Block #73,869,193

25 transactions · 17 stateful · 2026-05-11 10:24:29 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,869,193  ·  25 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x146d7940…d263

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5a1cd68f…4125

0x754704…b603

4 touches
1 conflict

0x269e4a33…fdd3

0x065c9d…c394

4 touches
1 conflict

0x33d611dc…2b65

0x065c9d…c394

4 touches
1 conflict

0x421c32c1…4629

0x754704…b603

4 touches
1 conflict

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity