← previous blocknext block →recent activity

Analyzing

Block #73,671,598

18 transactions · 16 stateful · 2026-05-10 12:16:47 UTC

Parallelism

89/100

Blocked

6%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,671,598  ·  18 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

0x2f7781d6…e632

0x34b655…2a6f

4 touches
1 conflict

0x97d5efed…1aa4

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x2b36ecc6…093e

0x3c2269…cf62

2 touches
0 conflicts

0xd2fc21b0…f410

0x3c2269…cf62

2 touches
0 conflicts

0xd4cd1c4d…6ae2

0x3c2269…cf62

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 0x2f7781d6c5…16e632

← previous block·next block →recent activity