← previous blocknext block →recent activity

Analyzing

Block #73,660,438

16 transactions · 13 stateful · 2026-05-10 11:01:27 UTC

Parallelism

88/100

Blocked

15%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,660,438  ·  16 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

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa486f342…64d5

0x34b655…2a6f

4 touches
1 conflict

0x97d5efed…1aa4

0x34b655…2a6f

2 touches
0 conflicts

0xa2a9347c…3a0a

0x34b655…2a6f

2 touches
0 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

2 touches
0 conflicts

0xb82bffbd…c6de

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 0x22e0cc1d4a…90ad04

← previous block·next block →recent activity