Block #73,493,125

← previous blocknext block →recent activity

Analyzing

Block #73,493,125

16 transactions · 13 stateful · 2026-05-09 16:25:38 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,493,125  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xed57bddf…1abf

0xc8689a…ee79

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x0175b7a6…1dba

0x6c4bfa…a540

6 touches
3 conflicts

0x0175b7a6…1dbc

0x6c4bfa…a540

6 touches
3 conflicts

0x0175b7a6…1dbd

0x6c4bfa…a540

6 touches
3 conflicts

0x0ef1e663…8f2a

0x6c4bfa…a540

6 touches
3 conflicts

0x1a4b4152…0a08

0x6c4bfa…a540

6 touches
3 conflicts

0x2e2214a9…fe0d

0x6c4bfa…a540

6 touches
3 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: 0xc8689a47…62ee79

3 conflicts on slot 0xed57bddf8e…bd1abf

← previous block·next block →recent activity