← previous blocknext block →recent activity

Analyzing

Block #73,478,166

9 transactions · 9 stateful · 2026-05-09 14:46:03 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,478,166  ·  9 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

0x1a5c8fa4…7071

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x79e191aa…2c82

0x065c9d…c394

3 touches
1 conflict

0x234f5ccf…f04d

0x065c9d…c394

3 touches
1 conflict

0x038c5ee6…d867

0x065c9d…c394

2 touches
0 conflicts

0x65377b4e…53c3

0x065c9d…c394

2 touches
0 conflicts

0x91a3ffa7…28c9

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x1a5c8fa4be…d77071

← previous block·next block →recent activity