← previous blocknext block →recent activity

Analyzing

Block #73,661,105

11 transactions · 9 stateful · 2026-05-10 11:05:58 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,661,105  ·  11 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

0x4ee0b65a…6d40

0x34b655…2a6f

4 touches
1 conflict

0x110a3804…f842

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xa345806f…8760

0x065c9d…c394

3 touches
1 conflict

0x06b019e1…cd46

0x34b655…2a6f

2 touches
0 conflicts

0x27dd9f70…2b05

0x34b655…2a6f

2 touches
0 conflicts

0x4f3a6b4a…3819

0x34b655…2a6f

2 touches
0 conflicts

0xa9988419…9f45

0x34b655…2a6f

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: 0x34b6552d…112a6f

1 conflict on slot 0x4ee0b65a93…c56d40

← previous block·next block →recent activity