← previous blocknext block →recent activity

Analyzing

Block #73,384,172

10 transactions · 7 stateful · 2026-05-09 04:20:31 UTC

Parallelism

70/100

Blocked

29%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,384,172  ·  10 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

0x8728cf1c…4751

0x065c9d…c394

4 touches
1 conflict

0xa7fe0d97…ae1c

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4ef1589b…41c6

0x065c9d…c394

4 touches
1 conflict

0x2d4bbab2…43e3

0x065c9d…c394

3 touches
1 conflict

0x899a486e…222c

0x065c9d…c394

3 touches
1 conflict

0x9b77ef5c…3d0e

0x065c9d…c394

3 touches
1 conflict

0xcb074908…56c7

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

1 conflict on slot 0x8728cf1c7d…3e4751

← previous block·next block →recent activity