← previous blocknext block →recent activity

Analyzing

Block #73,867,458

15 transactions · 14 stateful · 2026-05-11 10:12:57 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,867,458  ·  15 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

0xb159af88…a9e7

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x150af51d…9c42

0x34b655…2a6f

4 touches
1 conflict

0x15d039e7…4bb6

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x4582e32d…1abe

0x34b655…2a6f

4 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: 0x065c9d28…a9c394

6 conflicts on slot 0xb159af880b…47a9e7

← previous block·next block →recent activity