← previous blocknext block →recent activity

Analyzing

Block #73,050,749

13 transactions · 11 stateful · 2026-05-07 15:22:24 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,050,749  ·  13 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

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0x140d9bd2…6ef1

0x065c9d…c394

3 touches
1 conflict

0x2a354a63…0515

0x065c9d…c394

2 touches
0 conflicts

0x3fa76237…31b3

0x065c9d…c394

2 touches
0 conflicts

0x6d1a7d4b…d2df

0x065c9d…c394

2 touches
0 conflicts

0x8e66da19…66b6

0x065c9d…c394

2 touches
0 conflicts

0xcc119c75…92c5

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: 0x34b6552d…112a6f

1 conflict on slot 0x22e0cc1d4a…90ad04

← previous block·next block →recent activity