← previous blocknext block →recent activity

Analyzing

Block #73,653,105

14 transactions · 11 stateful · 2026-05-10 10:12:03 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,653,105  ·  14 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4a939bd5…253c

0x065c9d…c394

3 touches
1 conflict

0x7bf5c52c…a33d

0x065c9d…c394

3 touches
1 conflict

0xd49762c9…1359

0x34b655…2a6f

2 touches
0 conflicts

0xedb848fe…6534

0x34b655…2a6f

2 touches
0 conflicts

0x143dba04…1b98

0x8d66a4…3095

2 touches
0 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity