Block #73,595,581

← previous blocknext block →recent activity

Analyzing

Block #73,595,581

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

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,595,581  ·  14 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x1c3d4f13…9f90

0x065c9d…c394

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0xb82bffbd…c6de

0x34b655…2a6f

2 touches
0 conflicts

0xf6476f21…3580

0x34b655…2a6f

2 touches
0 conflicts

0xfa2527aa…9dd5

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity