← previous blocknext block →recent activity

Analyzing

Block #73,655,105

30 transactions · 25 stateful · 2026-05-10 10:25:35 UTC

Parallelism

73/100

Blocked

48%

Avg conflicts / tx

1.27

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,655,105  ·  30 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x05cb4c4f…26c4

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0x0175b7a6…1dbc

0x6c4bfa…a540

6 touches
3 conflicts

0x0c89ea7e…13eb

0x6c4bfa…a540

6 touches
3 conflicts

0x0ef1e663…8f2a

0x6c4bfa…a540

6 touches
3 conflicts

0x2e2214a9…fe0d

0x6c4bfa…a540

6 touches
3 conflicts

0x50997ada…364d

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: 0xd32edf66…9fff58

28 conflicts on slot 0x05cb4c4fee…9926c4

← previous block·next block →recent activity