← previous blocknext block →recent activity

Analyzing

Block #73,811,415

24 transactions · 13 stateful · 2026-05-11 03:59:38 UTC

Parallelism

88/100

Blocked

31%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,811,415  ·  24 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

0xe456e328…87d5

0xd32edf…ff58

5 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

4 touches
1 conflict

0x3577138e…6c47

0x065c9d…c394

4 touches
1 conflict

0x4039b31f…0f4a

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

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: 0xd32edf66…9fff58

3 conflicts on slot 0xe456e328b3…0887d5

← previous block·next block →recent activity