← previous blocknext block →recent activity

Analyzing

Block #73,513,684

10 transactions · 6 stateful · 2026-05-09 18:42:27 UTC

Parallelism

80/100

Blocked

17%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,513,684  ·  10 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

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0x91ea11d8…d27c

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0x45fd2360…df0e

0x065c9d…c394

2 touches
0 conflicts

0x5d4fabcd…4998

0x065c9d…c394

2 touches
0 conflicts

0x69188557…cc99

0x065c9d…c394

2 touches
0 conflicts

0x9b1bf429…e002

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xae69c12575…722379

← previous block·next block →recent activity