← previous blocknext block →recent activity

Analyzing

Block #73,469,893

18 transactions · 13 stateful · 2026-05-09 13:51:03 UTC

Parallelism

83/100

Blocked

31%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,469,893  ·  18 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

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0x1a4b4152…0a08

0x6c4bfa…a540

6 touches
3 conflicts

0x2e2214a9…fe0d

0x6c4bfa…a540

6 touches
3 conflicts

0x3e4b8d9f…b8a7

0x6c4bfa…a540

6 touches
3 conflicts

0x50997ada…364d

0x6c4bfa…a540

6 touches
3 conflicts

0xc5564f8e…f4bf

0x6c4bfa…a540

6 touches
3 conflicts

0xf0f673fd…37a7

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