← previous blocknext block →recent activity

Analyzing

Block #73,811,477

9 transactions · 8 stateful · 2026-05-11 04:00:01 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,811,477  ·  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

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xab6c495a…75e9

0x065c9d…c394

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xd244d0a2…1d63

0x065c9d…c394

3 touches
1 conflict

0x819a7044…f9a0

0x065c9d…c394

3 touches
1 conflict

0x27c72836…f61a

0xd32edf…ff58

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

3 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity