← previous blocknext block →recent activity

Analyzing

Block #73,837,448

23 transactions · 17 stateful · 2026-05-11 06:52:49 UTC

Parallelism

83/100

Blocked

41%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,837,448  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb81d3ee7…3947

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x2b422dd7…355f

0x065c9d…c394

4 touches
1 conflict

0x399082fb…efd8

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x9a7297a4…732b

0x065c9d…c394

4 touches
1 conflict

0xd858ae86…004e

0x065c9d…c394

4 touches
1 conflict

0xe50d11b1…231c

0x065c9d…c394

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

6 conflicts on slot 0xb81d3ee780…143947

← previous block·next block →recent activity