← previous blocknext block →recent activity

Analyzing

Block #73,673,604

17 transactions · 15 stateful · 2026-05-10 12:30:23 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,673,604  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x529acb6a…fcc6

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xcd6eabb2…6596

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xcd3c8154…0e90

0x065c9d…c394

3 touches
1 conflict

0x9e9d86fe…dd6f

0x065c9d…c394

3 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: 0x065c9d28…a9c394

6 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity