Block #73,926,002

← previous blocknext block →recent activity

Analyzing

Block #73,926,002

10 transactions · 8 stateful · 2026-05-11 16:42:54 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,926,002  ·  10 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

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0x8a85cf3d…2868

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0xb142d1c0…fe1e

0x34b655…2a6f

4 touches
1 conflict

0xe4f0f159…0c50

0x34b655…2a6f

4 touches
1 conflict

0x678d790b…6882

0x34b655…2a6f

2 touches
0 conflicts

0x693d979a…f2bd

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 0xf853eb8e72…d84027

← previous block·next block →recent activity