Block #73,596,326

← previous blocknext block →recent activity

Analyzing

Block #73,596,326

14 transactions · 13 stateful · 2026-05-10 03:51:33 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,596,326  ·  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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xf44cc08a…a344

0x065c9d…c394

4 touches
1 conflict

0x4bfdd5fb…d52b

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x12b6e339…1c7e

0x065c9d…c394

4 touches
1 conflict

0x5756f106…e33d

0x065c9d…c394

3 touches
1 conflict

0x1cd07e86…3ba9

0x065c9d…c394

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity